On Tue, Sep 2, 2014 at 2:35 PM, Warren Young <war...@etr-usa.com> wrote:
> If you have more than one computer connected to a VCS and at least one is > mobile, you should be using a DVCS. Fossil vs Git is a side issue, when it > comes to that. > I do and I use Fossil (no surprise there, right?) because of the simplicity of set up. (This is also why I've been advocating for the uber-patch feature. It lets > outsiders contribute patches to a project they don't have commit > permissions on, without making the one applying the patch do the work of > disentangling many unrelated elements of the patch.) This could be done using the --incremental feature of fossil export / import. It's just tricky to use. My experience with submitting patches (several different projects) has been (a) each patch must be limited to one fix or enhancement, and (b) should not result in merge conflicts when the dev applying the patch applies the patch. (Generally this means pulling the latest, merging, resolving, building and testing, then pulling and merging again to make sure. Then create the patch and send it as quickly as possible.)
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
