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

Re: svn status proposal

From: Philip Martin <philip_martin_at_ntlworld.com>
Date: 2001-09-16 04:33:00 CEST

Greg Stein <gstein@lyra.org> writes:

> $ svn status
> produces
> M foo.c
> and
> $ svn status -u
> produces
> M 58 102 102 foo.c

I like this as well, all the information is there, no extraneous
brackets. Just like other Unix commands ps, ls, w. Definitely the way
to go.

However to open another can of worms, how if at all, is branch
information going to be shown?

Version numbers on a branch look like MMMM.BB.VVV, according to
svn_fs.h, where MMMM is the mainline version that was branched, BB is
the branch number and VVV is the version on the branch. I assume a
branch from a branch looks like MMMM.BB.VVV.BB.VVV. This is of more
than academic interest to me: for the last project I worked on the
project's "main-line" was a branch, and all development was carried
out on a branch from from that branch. The ClearCase config spec would
be set up to show files from the development branch, then from the
project branch, and then from the main-line. Most of the time I am
only interested in the final VVV, but sometimes I want to know which
files are unchaged on my branch, and which files are unchanged on the
project branch:

So, we need another(!) option. For example:

$ svn status -u
M 58 1 102 bar.c
M 58 1 102 foo.c

indicates no committed changes on my development branch, and

$ svn status -u --branch
M 3333.4.777.6.58 2789. 3333.4.777.6.102 bar.c
M 3333.4.777.6.58 3176. 3333.4.777.6.102 foo.c

indicates that there are no committed changes for foo.c on the project
branch, but that there are committed changes for bar.c.

However this is much less readable than the ClearCase equivalent,
which shows the tags associated with the project/development
branches. From memory it get presented something like

$ cleartool ls

Perhaps rather than overload the status command we need a new command

$ svn branch
M bar.c 2789.
M foo.c 3176.

Will subversion branches have tags/names?


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.