Thus said Piotr Orzechowski on Tue, 07 Apr 2015 19:46:22 +0200: > If they can happen when two people push to central repository one > after another, then IMHO they should be blocked. Or at least there > should be a possibility to enable/disable some kind of lock mechanism.
I wonder just what this means? What part of the sync should be blocked? If I'm not mistaken, Fossil's design prefers to have the fork than not. > I agree that good communication is essential, yet I also think the > best way is to make software actively protecting us from making forks > by accident. The software already warns users that a fork is imminent. They have the choice to ignore the warning, or not. Andy -- TAI64 timestamp: 4000000055248f46 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
