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

Re: List of files passed to stdin in post-lock hook???

From: David Glasser <glasser_at_davidglasser.net>
Date: Tue, 12 Feb 2008 23:43:22 -0800

On Feb 12, 2008 11:23 PM, Lorenz <lorenznl_at_yahoo.com> wrote:
> David Glasser wrote:
> > Michael Weave wrote:
> >> I am using tortoise to lock files in a repository served up via
> >> svnserve.exe. When I get locks on multiple files I get multiple emails. I
> >> never see a list on stdin when the post-lock hook runs and its run multiple
> >> times. According to the literature I should be seeing a list of paths one
> >> per line? What do I need to do to set this up properly? Any help is
> >> greatly appreciated.
> >
> >This question is best asked on users_at_subversion.tigris.org, but:
> >
> >if you look in the sample post-lock script, you'll see
> >
> ># The paths that were just locked are passed to the hook via STDIN (as
> ># of Subversion 1.2, only one path is passed per invocation, but the
> ># plan is to pass all locked paths at once, so the hook program
> ># should be written accordingly).
> >
> >This is still the case.
>
> but as the OP mentions the hooks is call once per locked file. That
> makes no sense if the file list is passed via stdin.
>
> Or is the OP using a pre 1.2 server?

Read the comment again. As of Subversion 1.2, and in fact 1.4 and
trunk as well, there is no atomic "lock multiple files command", so
even if you put multiple paths on the "svn lock" line, only one path
will be passed per invocation of the hook; it will be called many
times.

--dave

-- 
David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-13 08:43:32 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.