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

Re: update vs status, where should local mods be displayed?

From: Philip Martin <philip_martin_at_ntlworld.com>
Date: 2001-09-13 23:57:01 CEST

[Oops, forgot to send to the list...]

Ben Collins-Sussman <sussman@collab.net> writes:

> Instead, I was thinking of something like:
> % svn status
> Repository Revision: 96
> _ 95 ( * ) ./ac-helpers/install.sh
> _ 95 ( ) ./ac-helpers/svn-apache.m4
> _ 95 ( ) ./ac-helpers/svn-macros.m4
> M 95 ( ) ./autogen.sh
> M 95 ( ) ./build.conf
> A 0 ( ) ./buildcheck.sh

I don't think moving the repository version moving to a separate line
is a good idea. It makes the remaining lines less useful, they don't
have all the information. Consider, as an example, usage like

% svn status | grep \\.h$

(or Mo's first post in this thread). Scripts that process svn status
output will also find this form less useful.

A file can have been modified in both the local directory and the
repository since the local version was last updated. There are
*three* version numbers that are of interest: the version in the local
directory, the last version with a change in the repository, and the
most recent version in the repository. I think I would want to see
all three version numbers explicitly in every line, certainly the
first two. Blank space instead of a number is not a good idea, it
makes separation into fields harder.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:41 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.