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

Re: Parseable output: --xml option for more commands

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2005-01-19 19:09:02 CET

Branko Čibej wrote:
> Julian Foad wrote:
>> If we start down this road, do we continue with the other
>> information-retrieval commands, and eventually also with the progress
>> output of action commands like "commit"? No, I don't think so.
> Yes I do think so. Why? Because parsing this commit and update output is
> important for clients that wrap the command-line client; psvn and vc-svn
> come to mind (although these would be happier with an --elisp option :-) .

Oh, that's OK then. When I wrote the above, I was concerned about us feeling
obliged to provide XML versions of everything just "for completeness". I have
no qualms about us providing XML output from all sorts of commands if it is
actually useful to people.

> The point is that if the format of the output produced by those commands
> changes, it's much easier for an existing parser to ignore unknown XML
> elements than to accomodate undeterministically changing column widths.


- Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 19 19:12:09 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.