Tim Moloney <moloney@mrsl.com> writes:
> Following the example of http://svn.collab.net/repos/svn/, I've
> created a repository that has the following structure
>
> /svn/project/trunk
> /svn/project/tags
> /svn/project/branches
>
> I know that the only difference between tags and branches is that
> tags won't (shouldn't) have anything commited back to them.
>
> Unfortunately, people make mistakes, is there a way to make the
> tags directory read-only to prevent accidental commits that would
> corrupt the tagged revision?
You could write a pre-commit hook that uses svnlook to determine which
paths were being modified. If the tags directory is being modified,
and if those mods were anything more than just the creation of a new
tag, the hook returns and error, and the commit doesn't happen. You
could even have the script send email to the would-be committer
saying, "I know what you tried to do, buck-o!"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 10 18:48:28 2002