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

Re: version control of 'hooks' directory

From: Greg Thomas <thomasgd_at_omc.bt.co.uk>
Date: 2005-06-02 10:13:39 CEST

On Wed, 01 Jun 2005 14:08:20 -0400, Christopher Ness
<chris@nesser.org> wrote:

>On Wed, 2005-06-01 at 12:15 -0500, kfogel@collab.net wrote:
>> Greg Thomas <thomasgd@omc.bt.co.uk> writes:
>> > Is there a reason why I can't make the svn-repos/hooks directory a
>> > working copy of something stored in the svn-repos repository?
>> I don't see any reason why it would be bad, as long as you have proper
>> authz controls. The security risks are obvious and are yours to
>> analyze :-).

Luckily, we'v got fairly tight control on our repository, so that side
of things is covered.

>If all of your users are trusted though this would be a good way for
>them to see why their commits are being rejected by the server and debug
>their own problems and suggest fixes.
>But of course you are writing good hook scripts that explain why things
>are rejected to STDERR aren't you. ;)

For pre-commit, of course. Getting information out of post-commit
hooks seems to be a bit harder :-(


This post represents the views of the author and does
not necessarily accurately represent the views of BT.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 2 10:17:48 2005

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.