Now I get it. Thanks for summing up your stance. Pozdrawiam / With best regards, Orzech
W dniu 07.04.2015 o 20:17, Ron W pisze: > I am saying warn. The louder the better. > > Naturally, when (a) auto-sync is enabled, and (b) you have > connectivity with your upstream, then it is POSSIBLE for the commit to > be "blocked" before the "fork" is committed. BUT, even then, there is > still a window of vulnerability for 2 (or more) commits to the same > parent. > > These accidental "forks" can and should be detected and warnings > issued. The louder the better. Everyone committing to the project > should see the warning. This way, it is less likely to accidentally > loose an orphaned commit. > > Also, an upstream automatically blocking an incoming commit is > anathema to Fossil's underlying promise to preserve the history. While > Fossil does have a shunning mechanism, it is driven by explicit human > intervention. This was designed that way because shunning discards > information. > > Far better to auto-add a special tag (via the existing mechanism for > adding tags to a commit) and have BOTH warnings displayed when the tag > is received and timeline provide special highlighting of commits with > the special tag.
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
