Re: When did a file last change?

Branko Čibej <brane@xbc.nu> writes:

> 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.

Oh c'mon, Brane. You want to look down a list of 20 items, and
*manually* notice exactly which ones have CR's greater than the
working rev? That's absurd. There's no way I want to think that
hard!

The whole point of the asterisk is to quickly scan down the column and
just instantly *know* what the next update will do, without doing
calculations. In particular, you can instantly predict conflicts by
looking for "M *" on the same line.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 27 03:56:14 2002