Re: preventing commits (this is *not* a classic hook question)

I have a pre-commit hook that stores its configuration inside your
repository. You'll need access to the Subversion server to set it up,
but once it's setup, you can control access by checking out the
control file from the repository, making your changes, and then
checking it back in.

This is a modification of a hook that I've been using for years.
Originally, the control file was kept on the server -- usually inside
the hooks directory. However, that meant logging onto the server, and
that was getting too difficult to do all the time. Besides, this way,
I can track who changed the control file and why.

What prevents anyone from changing the control file? The control file
is configured, so only the administrators can modify it.

You can take a look at it at
https://github.com/qazwart/SVN-Precommit-Kitchen-Sink-Hook. (Yes, a
Subversion hook is stored in GitHub). If you need any further help,
contact me at david_at_weintraub.name, and I'll see what I can do.

-- 
David Weintraub
qazwart_at_gmail.com