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

Re: post-commit error printet to stdout (was: Re: svn trunk r17226: FAIL (x86_64-unknown-linux-gnu static ra_local bdb))

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2005-11-07 23:35:16 CET

On 11/7/05, Peter N. Lundblad <peter@famlundblad.se> wrote:

> Fun. I looked in the file, but didmiss that comment. Sometimes using a
> one-line braille display shows up:-)
> This was committed recently as part of 443.
>
> Is the above statement really valid? We print other warnings to stderr. If
> someone wants to know if the commit failed, then they should use the exit
> status IMO. Hmmm, and then we have the proposal that warnings should also
> set a non-zero exit status... I still don't think printing this particular
> warning to stdout is a good idea. The commit has succeded, but you don't
> know how severe the post-commit failure is.

I don't feel strongly one way or the other on this. If we are sending
other warnings to stderr I guess it does make sense to treat this the
same way though.

Madan, since you wrote that code, what do you think?

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 7 23:36:35 2005

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