Option #2 is much better for XML since it is "proper" as an empty document
is not valid XML as it must always have a root node.
Ex:
Empty xml:
<?xml version="1.0"?>
<status/>
Or
<?xml version="1.0"?>
<status>
</status>
Or non empty xml but empty target:
<?xml version="1.0"?>
<status>
<target path="."/>
</status>
Or
<?xml version="1.0"?>
<status>
<target path=".">
</target>
</status>
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Sr. Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you
have received it in error, purge the message from your system and
notify the sender immediately. Any other use of the email by you
is prohibited.
-----Original Message-----
From: Daniel Rall [mailto:dlr@collab.net]
Sent: Monday, February 12, 2007 12:56
To: Jason Pyeron
Cc: dev@subversion.tigris.org
Subject: Re: svn status -u --xml
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.
Thoughts?
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: dglasser@gmail.com [mailto:dglasser@gmail.com] On Behalf Of David
> Glasser
> Sent: Sunday, February 11, 2007 16:22
> To: Daniel Rall
> Cc: Jason Pyeron; dev@subversion.tigris.org
> Subject: Re: svn status -u --xml
>
> On 2/11/07, Daniel Rall <dlr@collab.net> 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
> <?xml version="1.0"?>
> <status>
> <target
> path=".">
> svn: warning: '.' is not a working copy
> </status>
>
> (Whether or not the stderr warning ought to get into the XML is
> another story...)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 12 19:07:49 2007