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

Re: making 'status' output more human readable

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-01-11 16:53:54 CET

On 1/11/06, Bart Robinson <lomew@pobox.com> wrote:
> What I was getting at with the -x option
> was to have a way to make svn's concise but arguably cryptic
> status output a little easier to read for newbies. I have some
> coworkers that are either uncomfortable with our current CVS (so
> they aren't used to its similar output) or very comfortable with
> perforce and I was thinking of some way to head off some of the
> questions that will come from interpreting svn output. I
> figured that since I was going to have to do *something* (write
> a script, wrapper, docs, etc) I might as well check to see if
> there were others that wanted it and just needed someone to
> actually do it.

It sounds like you're *anticipating* that people will be confused by
the output of 'svn status'. Have you actually run into a problem yet?
 I'm wondering if you're just inventing problems before they exist.
Thousands of people use 'svn status' obsessively -- newbies and
experienced users alike -- and I've never heard reports of confusion
about the output before. 4 letter codes really aren't that big a
deal. :-)

Besides, you didn't actually expect that you would switch version
control systems and *not* have to retrain people, did you? Or rewrite
bunches of your work processes? :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 11 16:55:51 2006

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.