Re: version control of 'hooks' directory

On 6/1/05, Greg Thomas <thomasgd@omc.bt.co.uk> wrote:
> I've been playing around with hooks a lot recently, and thought I'd
> better put them under version control.
>
> 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've
> tried it - it seems to work, despite the horribly recursive nature of
> it, but I'm wondering if there's a good reason why I shouldn't be
> doing it.

I believe in version controlling everything, and that would include
scripts that control my version control system.

I recommend that you store the hook scripts in a separate archive with
its own permissions and rules and not part of your main project. That
way, you have better control over access.

You wouldn't get into a situation where an error in the hook script
keeps you from committing a change in your hook script that would fix
the error. If you simply changed the hook script without committing
it, you could still fix the error (and then commit the fixed script to
your archive).

--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org