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

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

From: Michael Hüttermann <michael_at_huettermann.net>
Date: Thu, 22 Mar 2012 10:45:26 +0100

Hi David,
thanks, that's awesome!

Michael

> 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
>
>
Received on 2012-03-22 10:45:58 CET

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.