an itch to scratch

I wanted to see what people think of this idea.

I have an itch: I run 'svn st -v', and it currently shows me the
working revision of each file. But I want to also know the last
revision in which each file *changed*. That's the info that really
matters.

Often I'll want to see the last set of changes made to a file: 'svn
diff -r N:HEAD foo.c' But the trick is determining N. If our 'svn
log' command were working properly right now, I could just view the
log of foo.c and figure it out. But here's the crazy thing: N is
already cached in the .svn/entries file. (The keyword $Rev$ expands
to it.)

So I'm proposing that we add this last-changed-revision as a new
column to 'svn st -v'. It's a verbose listing, after all. And while
someday it may end up being redundant with 'svn log foo.c', I have no
problems with redundancy in the long run.

Thoughts? If people like this idea, maybe we can list it as a
very easy bite-sized task.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:56 2006