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

Re: Future-proofing "svn st" output

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-08-05 18:39:49 CEST

Gareth McCaughan <Gareth.McCaughan@pobox.com> writes:
> 4. Offer some separate way for third-party programs to discover
> which columns they need. For instance, an option that makes
> "svn st" output a list of field names and columns.
> This is another option-proliferating approach, though the
> proliferation is fairly mild. It has the dubious advantage
> that the show-me-the-column-definitions option could give
> the information in a form that's friendly to humans as well
> as to computers.
> The same goes, mutatis mutandis, for other Subversion commands.
> "svn st" seems clearly the most important, though.

I like this solution best, personally.

It does not really cause more option-proliferation, because it stops
after this one new option. And as you said, it's both human and
computer friendly.

> I can't quite shake off the feeling that I may be worrying
> about a non-problem; but I also can't see why it's a non-problem.
> Am I missing some obvious reason why none of this matters?

I think we can't be sure yet whether it's a problem, because we don't
know what the future holds for "svn st". But if we ever get into a
corner, now at least we have some solutions ready.

> I remark that the widths of the columns for "svn st -v" are
> different in all three of (1) the output of "svn help status",
> (2) the examples in the Handbook, and (3) the actual output.

:-) Oops.

Ummm, care to send in a patch? (Hey, can't hurt to try...)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 5 18:55:22 2002

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.