Post-commit push

["Harvey, Edward" <Ed...@patni.com>]

There's a directory which is versioned, and some people keep a working copy of it in their home dir, while others share a working copy.  The users who have their own working copy sometimes commit changes, and forget to go update the common area.  Is it a bad idea to create a post-commit hook which will go into that area and do "svn update?"  Is there a more elegant or advisable solution to push changes for a specific folder?

Thanks....

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Post-commit push

[Paul Koning <Pa...@dell.com>]

>>>>> "Edward" == Edward Harvey <Harvey> writes:

 Edward> There's a directory which is versioned, and some people keep
 Edward> a working copy of it in their home dir, while others share a
 Edward> working copy.  The users who have their own working copy
 Edward> sometimes commit changes, and forget to go update the common
 Edward> area.  Is it a bad idea to create a post-commit hook which
 Edward> will go into that area and do "svn update?"  Is there a more
 Edward> elegant or advisable solution to push changes for a specific
 Edward> folder?  Thanks....

I've done exactly this, to "publish" source controlled hook scripts to
a directory where each of my repository hooks link to.  Also, for the
configuration scripts and other stuff for the ViewVC setup, and for
the access control data.  Works very nicely.

    paul


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org