W dniu 07.04.2015 o 18:03, Ron W pisze: > I don't think they should be blocked, but the upstream repo should > detect them and warn about them. 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.
W dniu 07.04.2015 o 21:20, Ron W pisze: > But the best way to avoid forks is good communication between > contributors. 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. E.g. block accidental forks on the same branch, but inform user, that there's a possibility to "--force" push. I'm talking about the git-like situation mentioned earlier. Just my $0.02. ;) -- Pozdrawiam / With best regards, Orzech
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users