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

Re: Split the functions of `cvs update'?

From: Karl Fogel <kfogel_at_galois.collab.net>
Date: 2000-10-27 17:39:34 CEST

Jim Blandy <jimb@savonarola.red-bean.com> writes:
> It would be nicer to have it be a straightforward extension of the
> `cvs update' output format, but the filename does need to come at the
> end (following ls's example).

The filename comes at the end in update too.. I think we can have our
cake and eat it too. The current "status" output format is not
written in stone; I think we should put the single letter status
indicator leftmost, as update does, followed by version info, followed
by the filename.

That was what Ben originally did, and I talked him out of it, because
I thought the status letter should be as near the filename as
possible. Now I'm thinking Ben's original way is better.

Anyway, the point is, Matt, I think your issue was merely with the
output format of "cvs status", not with its semantics.

> In the future, of course, this will probably be refined not to waste
> columns reserving space for large version numbers that don't appear
> (hmm, or maybe fixed-width fields are better), to say "(r none)" in a
> way that creates less noise to tell us nothing, etc. But those are
> refinements.

Yah. You have to know the widest number in advance, that's the only
thing. Anyway, refinements for the future.

> One idea I had in my command-line notes was a "script" prefix for
> commands --- it could be a global flag, too --- which adjusts the
> syntax of the output for reliable parsing by scripts. Colon-separated
> fields, simpler argument parsing, or whatever folks feel is useful.

If we could achieve auto-parseable default outputs that are also human
readable, that's even better. Let's try for that way first. CVS
*almost* manages it in a lot of places -- and the changes that would
be necessary to make things fully script-friendly are usually ones
that would make the output more human-friendly too, I think.


> ------- Start of forwarded message -------
> To: dev@subversion.tigris.org
> Subject: `svn status' details
> From: Ben Collins-Sussman <sussman@newton.collab.net>
> Date: 24 Oct 2000 17:45:22 -0500
> Message-ID: <86vguhamf1.fsf@newton.collab.net>
> Implemented `svn status' command. Here are some details, especially
> for people thinking about user interfaces. (Output is quite terse
> right now, just as Karl likes it. :))
> The output format is
> <local_ver> (r <repos_ver>) <flag> <name>
> ...where <flag> is one of {A, D, M, -} if the dirent is marked for
> (A)ddition, marked for (D)eletion, locally (M)odified or (-)
> unchanged.
> Here are some examples:
> [sussman@newton:~]$ ./svn status t1/iota
> 1 (r none) - t1/iota
> [sussman@newton:~]$ ./svn status t1/A/D/gamma
> 1 (r none) M t1/A/D/gamma
> [sussman@newton:~]$ ./svn status t1/A/D
> 1 (r none) - t1/A/D
> Notice in the last example that we're getting the status of a
> *directory*. Yummy.
> ------- End of forwarded message -------
Received on Sat Oct 21 14:36:13 2006

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