Greg Goodrich wrote:
>> or something equivalent and have that affect the entire subtree below
>> it, preventing commits to it.
>>
>> But today we can't. (Something for a pre-commit hook? I've never
>> written one..)
>
> The precommit hook is nice, but seems a bit underpowered for locking
> things down in this way. For example, I would like my tags area to
> allow tags to be created in there, but never modified. Well, when you
> do an svn copy, the pre-commit hook gets called, so now you have to be
> able to differentiate between a copy and a normal commit, which it
> doesn't seem is an easy thing to do. I investigated the svnlook
> command, but it doesn't appear that there is really a good way to use
> that command to be able to tell the difference between a copy and a
> commit. The only mechanisms I can come up with for this are somewhat
> hacks (running grep on the output for "^A" versus "^U" for example).
We already have a pre-commit hook that does exactly what you want. See
http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/svnperms.py
http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/svnperms.conf.example
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 7 00:17:54 2004