[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: Joe Orton <joe_at_manyfish.co.uk>
Date: 2001-09-14 00:00:26 CEST

On Thu, Sep 13, 2001 at 01:25:06PM -0700, Mo DeJong wrote:
> % svn status
> N ./ac-helpers/install.sh
> M ./autogen.sh
> M ./build.conf
> A ./buildcheck.sh

Hoorah - this is pretty close to how my opinion of how "svn status"
should work. SVN currently has unreadable status output as well as CVS!
(until you read the docs and find -M)

Note that by eradicating that annoying and useless "remote repos
revision" field, you also eradicate the need to go to the server, so
this is an entirely local thing. Which is IMO how it should be. And you
can get rid of lots of the annoying whitespace too.

I don't understand why people want to overload the "status" command with
doing updatey things. "status" should show me the status of the WC - end
of story. If you want some kind of "will an update change my WC"
command, add a --dry-run to "update", like make has, or something.


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.