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

Re: Problems with post-commit hook updating working copy

From: Alejandro Fernandez <alejandro.fdez_at_gmail.com>
Date: 2007-01-24 11:16:03 CET

2007/1/23, Ryan Schmidt <subversion-2007a@ryandesign.com>:
>
>
> On Jan 23, 2007, at 05:55, Alejandro Fernandez wrote:
>
> > I'd like to "make a pipeline" to join the ouput of the hook script
> > with the svn client console. Is this possible?
>
> I don't understand exactly what you're trying to do?

.. but it seems you do....

A post-commit hook cannot send any output back to a Subversion client.

That's what I'd like!
I'd like to receive the results of the svn update called from the hook, but
as you say it's not possible.

So now the question could be: is this functionality desired by the users? I
think it could be treated by the designers and/or programmers of svn.

Is there any mechanism to propose an improvement?

A pre-commit hook can send error output back to the client in the
> event of a problem. (If you exit your hook with a nonzero status
> code, anything you've printed to stderr gets shown on the client.)
>
> If you want the post-commit hook to initiate some kind of
> communication with the user, it will have to happen via an outside
> channel, such as by sending the user an email.
>
>
> --
>
> To reply to the mailing list, please use your mailer's Reply To All
> function
>
>
>

-- 
Saludos,
Alejandro F.
Received on Wed Jan 24 11:16:33 2007

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.