On Sun, 13 Jan 2013 16:35:11 +0100, Ramon Ribó <ram...@compassis.com> wrote: > In my opinion, the solution is more simple. Instead of: > > - sync > - stop if would fork > - commit > - sync > > The procedure should be: > > - commit > - sync > - rollback if would fork
There is no rollback, an commit has been done. I suppose you mean to reverse the commit, but you can't do that. Apart from it being a key part of fossil that everything is immutable, you still can't do it. Which repository do you undo the commit in, the one synced to or the one synced from? What happens to other repositories? What if someone else does a commit based on the one you are reversing? The only way to deal with those is to stop fossil being distributed! Anyway the issue is not that forks can happen (which is inevitable), but that users should know they have happened and be able to deal with them. Eric -- ms fnd in a lbry
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
