One feature "missing" from Fossil is a way to restrict checkins on the 'trunk' (or other branch) to certain people.
This is necessary in a group where the methodology is for a "gatekeeper" to approve integration into the main line of development. Has there been any thought along those lines? In my perfect scenario, a branch (including trunk) may have an ACL list which would restrict who could do what operations on it. The way I envision it working is that if a branch has an ACL, it would get checked against the current user and kind of access, which would be approved accordingly. In current practice, I have two repositories, one with "golden" code and another to which any developer can contribute. This is a little bit painful, as you can imagine. Thoughts? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
