[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: commit-access-control.pl for branch/tag naming conventions

From: Nico Kadel-Garcia <nkadel_at_comcast.net>
Date: 2006-07-27 00:00:46 CEST

Justin Johnson wrote:
> Hi,
> I'm trying to us commit-access-control.pl to enforce branch and tag
> naming conventions. I setup commit-access-control.cfg as follows.
> [Make everything read-only for all users]
> match = .*
> access = read-only
> [Make trunk read-write for all users]
> match = ^trunk
> access = read-write
> [Enforce branch naming conventions]
> match = ^branches/(RB|BUG|TRY)-
> access = read-write
> [Enforce tag naming conventions]
> match = ^tags/(REL|PRE|POST)-
> access = read-write

Use svnperms.conf and svnperms.py. I'm really a broken record about this
lately, but I find its syntax much more robust. The ability to allow anyone
to create tags, but no one to edit them, but a site manager to delete them,
is amazingly helpful in enforcing policy.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 27 00:02:45 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.