On 9/1/2014 15:49, Scott Robison wrote:
the reasons I use fossil have little to do with its distributed nature (though I'm using it more often that way as time goes by).
A DVCS can be useful even to a lone developer. Several times since switching from svn to Fossil, I've spent some of my disconnected travel time working on a project backed by Fossil, and was able to check in changes while offline, knowing I can synch later, with every detail of my change history synched discretely, rather than as a monolithic blob.
When doing the same kind of work in my svn days, I'd end up with these massive diffs that I had to spend a bunch of time disentangling in order to get sane checkin comments on each aspect of the change set.
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.
(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.)
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
