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

Re: an itch to scratch

From: Michael Wood <mwood_at_its.uct.ac.za>
Date: 2002-01-16 09:49:20 CET

On Tue, Jan 15, 2002 at 12:21:20PM -0600, Karl Fogel wrote:
> Ben Collins-Sussman <sussman@collab.net> writes:
> > Actually, now that I think about it, this is identical to doing 'svn
> > diff -r HEAD', no? The use case I want is to see the last set of
> > changes made to a file. Thus I want to see
> >
> > svn diff -r ($Rev$ - 1):HEAD
> >
> > maybe this could look something like
> >
> > svn diff -r PREVIOUS:HEAD
>
> This is not the "last set of changes made to a file". $Rev$
> could be any number of changes behind HEAD. Therefore, $Rev$
> - 1 could be one more than any number of changes behind HEAD.
> :-)

Why is this not the last set of changes made to a file? If
$Rev$ is the "the revision in which the file last changed"
(which happens to be any number of changes behind HEAD) then
$Rev$ - 1 must be the revision just before the last change to
the file.

The contents of the file should not have changed between $Rev$
and HEAD, should they?

> I think what you meant is
>
> svn diff -r PREVIOUS:CURRENT
> svn diff -r PREVIOUS:
>
> which would all do the same thing:
>
> svn diff -r ($Rev$ - 1):$Rev
>
> Is that right? (You could get the reverse order in the
> obvious way, of course.)

That's more explicit, but when you're just looking for the "last
changes to this file," it's the same thing.

Anyway, that's probably splitting hairs :)

-- 
Michael Wood <mwood@its.uct.ac.za>
---------------------------------------------------------------------
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

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.