Thus said Abilio Marques on Mon, 11 May 2015 09:27:53 -0430: > I wondered back then, what would it take to implement this for fossil. > The first thing that popped to my head was the protocol. I gave a > quick glance back then, and I recall seeing no way of detecting a > "push" to a specific branch. All I saw were deltas and stuff like > that.
While this is not possible as a protected branch with Fossil, it certainly is possible to setup your workflow such that there is a ``golden master'' copy of the repository on a specific host. Pushes to this host will be done only by one person whose responsibility it is to review all the changes in the repository before they are pushed to the ``golden master'' host. Nobody else is allowed to push to this host. It's not quite the same as a protected branch, being rather a protected clone, but it does allow one person (or a set of people) the opportunity of reviewing *all* changes before syncing. They can correct things as necessary before syncing to the ``golden master'' host. Thanks, Andy -- TAI64 timestamp: 400000005550fff4 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
