I don't think "autosync on" depends on the size of the development team. For me it was more a problem due to disconnected repo's from VPN timeouts or actually offline. We turn off autosync and manually push and pull as needed. That way, we are never caught off guard.
On Fri, Jul 19, 2013 at 12:08 PM, Lluís Batlle i Rossell <vi...@viric.name>wrote: > On Fri, Jul 19, 2013 at 01:43:15PM +0200, Stephan Beal wrote: > > On Fri, Jul 19, 2013 at 11:57 AM, Lluís Batlle i Rossell > > <vi...@viric.name>wrote: > > > > > I think I wrote this before, but I use autosync, and I often end up > making > > > a > > > "fossil merge" of a locally-outdated branch. It's quite annoying. :) > > > > > > Should fossil merge autosync before attempting the merge, if autosync > is > > > set? > > > > > > > If it did that then it would do a sync where none is required for the > > majority of cases, and that sync would fail if the user is offline. That > > would force the majority-case user who is offline to turn off autosync > > before doing any merging. > > You could say the same about "fossil update" for switching branches, or > committing, and they do autosync. I don't see why "fossil merge" should be > different. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
