So we're producing malformed/incomplete output on stdout for 'status'
and 'info' when in --xml mode. When not in --xml mode, there's no
output at all on stdout (nothing to report on). In both cases, we
write an error message to stderr.
We should either:
1) Produce no output on stdout (nothing to report on).
2) Produce well-formed output on stdout.
...and continue to write the error message to stderr. I prefer option
#1; since we consider this an error condition (and produce and error
message), there's little point in sending any output to stdout.
On Sun, 11 Feb 2007, Jason Pyeron wrote:
> Yes this error occurs for non working copy directories.
> Since the error message goes to stderr, it is of no importance to me.
> By the way this happens for 'svn info --xml' too.
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of David
> Sent: Sunday, February 11, 2007 16:22
> To: Daniel Rall
> Cc: Jason Pyeron; email@example.com
> Subject: Re: svn status -u --xml
> On 2/11/07, Daniel Rall <firstname.lastname@example.org> wrote:
> > This problem doesn't seem to exist on trunk:
> I think Jason was implying you needed to be in a non-working copy
> directory to see it. Note that there's also some stderr output, and
> -u is not required:
> 30-5-39:/tmp glasser$ ~/Projects/Subversion/trunk/subversion/svn/svn st
> <?xml version="1.0"?>
> svn: warning: '.' is not a working copy
> (Whether or not the stderr warning ought to get into the XML is
> another story...)
Received on Mon Feb 12 18:56:47 2007
- application/pgp-signature attachment: stored