On Mon, May 11, 2015 at 10:51 AM, Abilio Marques <abili...@gmail.com> wrote:
> > Note also that this goes against one of the founding principles of >> Fossil: that the VCS should implement mechanism not policy. That is >> to say, details of who should be able to check-in to which branches >> and whatnot should not be enforced by the VCS. Project policies need >> to be enforced by some other means. >> >> > Haven't thought about it that way. I confess I've read that principle a > couple of times on other emails. > Another possible work-around (besides what Andy and I suggested) would be for contributing devs to mark their trunks (and other designated "protected" branches) as private. Then, when working on a feature/fix branch, "fossil publish branchname" to make that branch push-able. While this won't prevent intentional pushes of commits on trunk (or other "protected" branches), it greatly reduces the risk of pushing accidental commits on trunk.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
