Re: Repository ACL's

Daniel Patterson wrote:

>A potential rule to meet both of these requirements (sort of) occurred
>to me the other day:
>
> Only the ACL on the most recent revision of a resource actually
> controls access.
>

It's tempting, but it doesn't work (as your own example shows). It's
quite reasonable to have one permission policy for the development
mainline branch (e.g., all-access for members of the development team)
but a different policy for a release branch (all-access for the release
manager, read for development and QA). Your proposal can't cover both.

Yes, it's a very tricky question. :-\

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org