I agree with it too, but how about taking it a step further, and adding
svn diff -r CURRENT:HEAD, which would use that $Rev$ info to determine which
node id to use for the diff.
On Tue, Jan 15, 2002 at 11:11:44AM -0600, Karl Fogel wrote:
> +1, I think this is a great idea!
>
> Ben Collins-Sussman <sussman@collab.net> writes:
> > 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
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- application/pgp-signature attachment: stored
Received on Sat Oct 21 14:36:56 2006