> > On 9/29/2010 11:11 AM, Alan Barrett wrote:
> >> I make my hooks directory a working copy of an appropriate subdirecrory
> >> in the repository (or in another repository), and use a post-commit
> >> hook to run "svn update" in the hooks dir when it sees a commit to the
> >> relevant path.
> Les Mikesell wrote on Wed, Sep 29, 2010 at 11:25:27 -0500:
> > Does that cause trouble when the post-commit script itself is updated
> > while running - or does svn always write new files and rename when
> > complete which should at least work on unix-like systems?
On Thu, 30 Sep 2010, Daniel Shahaf wrote:
> I'm pretty sure we don't let you end up with a half-written file in the
> working copy.
>
> But let's hope the 'svn update' never runs into a conflict, or things
> are going to get interesting....
Yes, things could get nasty if there are conflicts, but that won't
heppen if you are careful not to leave uncommitted changes lying around
the hooks directory.
The only problems that I have encountered have been when I edit in
the hooks directory itself (instead of in a separate working copy),
run "svn commit", and then have the post-commit hook try to run "svn
update" while the directory is still locked by the outer "svn commit"
process. This causes the inner "svn update" to fail, with harmless
error messages.
--apb (Alan Barrett)
Received on 2010-10-01 10:56:24 CEST