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

update output idea

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-04-26 15:07:19 CEST

Hey, I just had a fleeting thought, wanted to see what folks think.
I've run this idea by kfogel and cmpilato, and they both like it.

More than once, an svn newbie has asked, "how do I find out what
version my working copy is at?"

The answer has always been, "well, there's no one magic way to know if
your working copy is all at one revision. you might have a
mixed-revision working copy, you just can't tell."

Usually, I also tell folks to run 'svn st -vn' at the top of their
tree. Generally every file in trunk/ will have the same working
revision number... and that's a pretty good guess. Most likely your
whole tree is at that revision.

So here's a new take on the situation: what if 'svn update' actually
printed a final feedback line, the way 'svn commit' does?

   % svn update
   Updated to revision 1788.

Then, after an update, you'd know exactly how recent you are (ignoring
your local mods), as opposed to using 'svn status' to hazard a guess.

It would be effortless to do this -- the update-editor already
receives a 'target revision' from the server right at the beginning of
the editor drive. Heck, checkouts would print the final line too,
since it's the same editor.

Anyone have objections? If not, I'll file it as a bite-sized task.
Or I'll just do it.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 26 15:10:33 2002

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.