stderr and $? indicate an
error condition?
Steven R. Loomis wrote on Tue, Jan 17, 2012 at 15:21:10 -0800:
svn info --xml gives malformed XML on error.. could it detect this
situation and still cleanup the XML, or not output any XML at all?
svnversion by comparison outputs 'exported'.
-s
$ svn
that one doesn't
have to parse screenfuls to get to it.
Errors on stderr are not rendered in XML.
Steven R. Loomis wrote on Wed, Jan 18, 2012 at 08:40:57 -0800:
Daniel,
I'm not asking to change the error condition.
I guess I would prefer to emit an error in XML format, or to emit
no XML at all
Shahaf wrote:
Well, yes, but backwards compatibility means that we have to keep it
returning an error ($? != 0 and stderr != ), or we'll break everyone
else's scripts.
If you have a suggested change that is backwards compatible, we'd love
to hear it.
Steven R. Loomis wrote on Wed, Jan 18, 2012
svn info --xml gives malformed XML on error.. could it detect this
situation and still cleanup the XML, or not output any XML at all?
svnversion by comparison outputs 'exported'.
-s
$ svn info --xml /tmp
?xml version=1.0 encoding=UTF-8?
info
svn: E155007: '/tmp' is not a working copy
$ svn
4 matches
Mail list logo
