[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: Scott Lamb <slamb_at_slamb.org>
Date: 2003-05-19 20:02:29 CEST

On Monday, May 19, 2003, at 12:45 US/Central, Greg Hudson wrote:

> svn diff [--old=old-target] [--new=new-target] [file1 file2 ...]

Plus a [-r M[:N]], I assume?

> Where a target is a wc path or url[@rev], and the file list is relative
> to new-target. old-target defaults to wc-base, new-target defaults to
> "." (meaning wc-current), and the file list also defaults to ".". I
> don't know if that would satisfy people today. svn compare would
> become
> "svn diff --old=foo --new=bar" with the implicit "." file list.

That's the first one I really like. It seems like it very naturally how
I use diff (like Justin's, but even more so - the repository I commit
the most to doesn't even have any branches/tags, so the most common
case is even more common). I think it supports everything anyone wants
to do, which none of the others can match. And the orthogonal
specification of target/file list with the default values really makes
clear what's going on. I think there would be a lot of confusion over
the exact difference between "diff" and "compare", especially since one
isn't a subset of the other (up/switch).

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 19 20:03:59 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.