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. > If you really want a technical means to enforce your policy, you could remove check-in permissions from the master repository. The owner of the master repo will still be able to make commits to it, and pull from other repos. The protection from accidental commits to trunk would come from having the integrator clone from the master then pull changes and review them. If there are any commits to trunk, the clone can be discarded. If the project is too big for re-cloning every time there is an accidental commit to trunk, then you could require the contributing devs to send "bundles" to the integrator. On import, commits from a bundle have a special status that allows them to be un-imported.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
