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

Re: update output idea

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-04-27 09:25:27 CEST

Mark <cm_mark@yahoo.com> writes:
> I don't know what the user can do with that info, a 'svn log -r1788 foo
> bar.txt' may likely not return anything if they where not involved in commit
> 1788.
> I don't know, I guess most on the list thought it was a good idea, I must be
> missing something. I am still trying to get used to a "svn st -vn" on a file
> telling me the the repository revision is 1796 but the file in my workarea is
> 1741, but it is up-to-date.

"svn st -v" output tells you both the highest revision number the
local file has seen, and the revision in which the file last changed.
It does *not* tell you the current head of the repository (you seem to
think it does, but you have to add the "-u" flag for that). So if one
understands the output of "svn st -v", one will not be confused.

The point of that extra line at the end is to tell you how far along
in the repository history you are. That way if you're looking at some
other source of information (say, browsing recent commits in the
repository, or seeing that a bug was committed in revision X), you can
remember that your tree is already past revision X, so you know you
got the fix.

It doesn't answer all questions, it's just a piece of information
that's useful in some circumstances, and costs little to give (one
line of vertical space is relatively cheap).


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 27 09:23:30 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.