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

Re: [Issue 1351] New - svn -r 939 log vs. svn -r 939 diff inconsistency

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-06-06 19:48:29 CEST

Olaf Hering <olh@suse.de> writes:

> http://subversion.tigris.org/issues/show_bug.cgi?id=1351
> Summary: svn -r 939 log vs. svn -r 939 diff inconsistency
> svn -r 939 log shows that one change entry
> svn -r 939 diff shows the entire diff to the working copy
> I would expect that both behave the same.
> And I would like to act svn -r 939 diff to behave the same as svn -r
> 939 log does right now: show the changes in the specified changeset
> only, not the entire 'history'.
> There are x:y ranges for the history.

I disagree here.

We just spent weeks debating about the 'svn diff' UI. 'svn diff' and
'svn log' aren't related commands at all. They're not supposed to be
related; if anything, 'svn diff' and 'svn merge' are meant to be
similar. But just because two commands take revision ranges doesn't
mean they're supposed to behave the same.

If you want to see to changeset N, run 'svn diff -rN-1:N'.

Otherwise, 'svn diff' with only one revision is defined to be a diff
between a revision on the server and the working copy.

'svn diff' is extremely complicated, and has to cover at least 5
different use-cases. I don't want to change its UI again just because
it's *possible* to interpret one of its syntaxes in a way that's
inconsistent with another subcommand. There are zillions of other
examples like this.

Different subcommands have different usages, and intepret the -r flag
differently (and appropriately.)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 6 19:50:16 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.