tla changes vs. baz status
Michael Ellerman
michael at ellerman.id.au
Wed Jun 22 01:09:24 BST 2005
On Wed, 22 Jun 2005 02:13, John Whitley wrote:
> On Jun 21, 2005, at 6:59 AM, Martin Pool wrote:
> > More seriously, the current default is meant to be a tradeoff between
> > being machine-parseable and being reasonably understandable. I used
> > to like 'svn status', but I think Aaron's right that having to refer
> > to the legend so often shows something is wrong.
>
> Here's a question: why tradeoff at all? Have "bzr status" default to
> a human-readable format that (in principle) may change from release
> to release to ease human understanding issues. Think of its output
> like compiler error messages: designed to aid the human user.
That's a good idea.
> Complement that with something like "bzr status --xml" that outputs a
> cleanly spec'd machine-readable format. With XML as the output, no
> one will have to mess about reinventing a parser for it in the first
> place. If an XML schema is available, then output from "bzr status --
> xml" can be run through a validator as part of the test suite.
And so is that.
BUT, people are going to want to script it with sh/awk/sed/etc, and XML isn't
going to keep them happy, they'll script against the plain text version.
cheers
--
Michael Ellerman
IBM OzLabs
email: michael:ellerman.id.au
inmsg: mpe:jabber.org
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050622/3fdcca2a/attachment.pgp
More information about the bazaar
mailing list