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

RE: Re: version control of 'hooks' directory

From: Brandt, Servatius <Servatius.Brandt_at_fujitsu-siemens.com>
Date: 2005-06-03 11:55:24 CEST

Greg Thomas wrote:

>On Thu, 2 Jun 2005 12:17:43 -0400, David Weintraub <qazwart@gmail.com>
>>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).
>TBH, I don't see that as a problem. I've a 'live' repository, and a
>'test' repository. Both have a 'hooks' directory that are a wc of the
>same area in the live repository. I'll develop and test the script in
>the test repository, and when I'm happy, commit them. Then I log on to
>the live system, and simply 'svn update' the live hooks. If anything
>goes wrong, I can just 'svn revert', and revisit them again on the
>test repository.

This is what I'm doing, too. Last week, when I searched the mail
archive for a method how to put the hook scripts under version control,
I found a tip by Mike Pilato, who suggested to add the 'svn update' to
the post-commit hook. Then committing from the test repository means
you get the live hooks automatically. It is also possible to put the
files in the conf directory under version control.

I'm going to send a tutorial to the list which describes how I did this.
Just wait a moment ...

- Servatius

Servatius Brandt Phone: +49 89 636-41504
Fujitsu Siemens Computers Fax: +49 89 636-48716
EP SW AD C++ Email: Servatius.Brandt@fujitsu-siemens.com

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 3 11:59:58 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.