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

Re: Deadlock on Post-Commit Script

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Mon, 24 Aug 2009 04:34:05 -0500

On Aug 24, 2009, at 04:08, Jake Stone wrote:

> That's odd since running svn update from the command-line on the
> server doesn't prompt for anything. Might this be because it's in a
> commit script?

When you run svn update from the command line on the server, are you
the same user as the one that's running it from the hook script?
Every user has their own auth cache.

> I also noticed that svn export works just as well; it seems to
> properly export the new HEAD from the repository, and it will
> overwrite old files it the "--force" directive is used. Is svn
> export a save way to do this, since I will never commit from this
> working copy?

My first reaction would be that svn export would take longer than svn
update, since svn export must export everything every time, whereas
svn update can update only the few parts that have actually changed
in that revision.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-24 11:35:02 CEST

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.