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

[Locking] svn up and svn st -u output, take 2

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-01-06 22:12:18 CET


I've been reworking the output proposals for svn st -u and svn update.

What info we want to give to the user:
For svn up, if the WC has a lock token that is no longer in the
repository, we remove it in the WC. We want the user to know that. Whether
it was broken or stolen doesn't matter. Actually we don't know what made
the token disappear and the user can check the current lock status with
svn info URL.

For svn st -u, we want to show:
- Whether there is a lock in the WC.
- Whether this lock is "out of date". This includes that we want to show
if there is a lock at all in the repository

I'd like to use the same symbols for svn up and svn st -u if possible.

My current proposal is as follows:

svn up adds an extra column. "!" in that column means "this lock token was
missing in the repository and got removed".

svn st -u uses K in the sixth column to show whtether the WC has a lock
(like plain svn status does). It uses column nine to show the repository
state. A space means that the WC and the repository are in aggreement,
that is, if the WC has no lock, the repo has no lock and if the WC has a
lock token, the repo has the same lock token. "!" means the repo has no
lock token (the WC lock was broken) and "~" means that the lock was stolen
and the repo has another token now.

The idea is that "!" stands for missing in the status output and ~ stands
for "another object staying in the way". It is not perfect consistency.

Who is going to knock this down? If you plan on doing that, please provide
a concrete and complete proposal:-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 6 22:25:50 2005

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.