[PATCH - BACL] Branch access control extension

Elifarley Callado Coelho Cruz elifarley at gmail.com
Wed Apr 14 07:29:33 CDT 2010


Benoit,

Maybe I just misunderstood what you said, but do you want to strip these
four sections:
[acl.deny]
[acl.allow]
[acl.deny.branches]
[acl.allow.branches]

And instead, put their configurations all inside the '[acl]' section?

Note that while the [acl.deny] and [acl.allow] sections map users to file
paths, the new sections [acl.deny.branches] and [acl.allow.branches] map
users to branches.

Cheers,
Elifarley


On Tue, Apr 13, 2010 at 15:52, Benoit Boissinot <bboissin at gmail.com> wrote:

> On Tue, Apr 13, 2010 at 7:24 PM, Elifarley Callado Coelho Cruz
> <elifarley at gmail.com> wrote:
> > Here's an example configuration:
> >
> > [hooks]
> > pretxncommit.acl = python:hgext.acl.hook
> > pretxnchangegroup.acl = python:hgext.acl.hook
> >
> > [acl]
> > # Works as before.
> > # Branch checks are performed before file checks.
> > sources = serve
> >
> > [acl.deny.branches]
>
> I don't think it should be in a separate section, all the acl config
> should go inside [acl].
>
> Cheers,
>
> Benoit
>



-- 
Elifarley Cruz

Profile: http://bit.ly/9hrz0P
Professional info: http://br.linkedin.com/in/elifarley
Google Reader: http://bit.ly/2W7JK2
Bookmarks: http://delicious.com/elifarley
http://twitter.com/elifarley
http://elifarley.amplify.com/
-

" Do not believe anything because it is said by an authority, or if it  is
said to come from angels, or from Gods, or from an inspired source.
Believe it only if you have explored it in your own heart and mind and body
and found it to be true.  Work out your own path, through diligence."
- Gautama Buddha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100414/e31d6cca/attachment.htm>


More information about the Mercurial-devel mailing list