[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: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2001-09-13 23:16:50 CEST

Greg Stein <gstein@lyra.org> writes:

> Well... that is enuf for my analysis. Basically, I think "svn status" should
> default to the -M switch. --verbose gives you info on all files. No real
> answer for "check the server for true update info."

See the my last post on this thread. I believe that 'svn status'
should show us information *simultaneously* about local mods and
impending patches. We use the first column to describe an impending
commit, and a different column to describe an impending update.

But yeah, I agree. 'svn status' with no switches at all should filter
out all the "boring" items that have no flags set. If you want to see
every file, add a verbose switch.

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.