On Fri, Jul 18, 2014 at 9:03 PM, Eric Rubin-Smith <eas....@gmail.com> wrote:
> in Fossil. For example, perhaps you wish that you could say "user A can > create check-ins but cannot open or close branches". > That would break down if someone tried checking in with the --close, --branch, or --integrate options, at least two of which are very useful when working with branches (as many devs prefer to). (b) If you are only worried about inadvertent check-ins then you can > always correct them after the fact. Keep in mind that > the branch on which a check-in was made is super easy to change > in Fossil. FWIW, we've done this in fossil once or twice when the trunk was in a questionable state. > (d) If, despite all that you, *really* want a new permission primitive, > it's probably not too hard to add yourself. And DRH's code is > pretty fun to hack against, as many here will attest to. :-) > It would be doable but not be really trivial. Several of the queries make use of the hard-coded list of users, and any number of commands might have to be updated to account for the new permission. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
