Re: When did a file last change?

Karl Fogel wrote:

>But the main point is, since the information is local anyway, I think
>it's safe to say that there will *always* be a way to get at it using
>the command-line client. Probably we'd add a new column to the output
>of "svn status -v" (rather than changing the meaning of the existing
>column), but either way, there'll be plenty of warning, and it'll be
>before 1.0.
>
>

No, please, I promise I'll be good, not another column ...

It's not necessary. "svn status" meanse "Tell me what you know about
this file". So, if you do a "svn st -v" to get

    _ 2711 2667 kfogel CHANGES

the correct interpretation is: "You have revision 2711, and the contents
were created in 2667 by kfogel." This information is always correct and
unambiguous. Now, if you do a "svn st -uv", you may well get:

    _ * 2711 2667 kfogel CHANGES

The above interpretation is still correct, you just add "but the file
has changed in the repository since then."

Now, if we change "svn st -u" to print the info that's current in the
repository, the second result might change to:

    _ * 2711 2767 jimb CHANGES

It's not enough to print the "current" last-changed rev number, you have
to print the author, too. Now that you've gone that far, it strikes me
that the asterisk in the second column is extraneous -- you _already_
know your working copy is not up-to-date, because the last-changed
revision is greater than the wc revision.

So, instead of adding another column, I vote for _removing_ one. And
if/when we do that, we can widen the "author" column from 8 chars to at
least something that'll hold the username of every Subversion developer. :-)

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org