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

Re: Resolution of 'svn diff' change?

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-05-20 05:06:26 CEST

On Mon, 2003-05-19 at 17:04, Brian Denny wrote:
> But really, *all* diff operations are comparative in nature

I agree, and I'd like to take this a little further:

We are always comparing two things. Sometimes we are narrowing the
scope of the comparison to particular files or directories within those
two things.

With the current syntax, when we "svn diff foo bar baz", we are
comparing the wc base with the wc, narrowed to foo, bar, and baz. When
we "svn diff -r 2:3 foo bar baz", we are comparing wc-url@2 with
wc-url@3, narrowed to foo, bar, and baz. When we "svn diff url@R1
url@R2", we are comparing url@R1 with url@R2, with no narrowing.

It's this observation which led me to propose "svn diff [-r M[:N]]
[--old=oldtarget] [--new=newtarget] [path ...]", and the more I think
about it, the more I think we'll be able to explain that command more
easily than we could explain anything else.

But if we do go with separate commands, I note that Perforce calls them
"diff" for the iterative case and "diff2" for the comparative case.
It's ugly, but it's relatively intuitive and we wouldn't be being
gratuitously different.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 20 05:07:29 2003

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.