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

Re: What does 'svn diff' do?

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2005-10-10 05:20:37 CEST

On 10/9/05, Malcolm Rowe <malcolm-svn-dev@farside.org.uk> wrote:

> The _only_ advantage I can see for this behaviour is that it permits you
> to see what local modifications have been performed to the file since it
> was copied, if any. But I'm fairly sure that if you wanted to know that,
> you could pass in the old and new targets explicitly: it shouldn't be
> the default.

This discussion has come up many times: should 'svn diff' show a
copied file as entirely added, or only the parts that have been
tweaked since the copy? There are legitimate uses for both cases, and
my memory is that we all want to support both cases. Historically,
it's been a waste of time to declare that one use-case or the other is

The hard question is (1) deciding which behavior is the default, and
which requires a switch, and (2) being consistent across all three
code-paths of 'svn diff'. I don't think we've done a good job of
achieving those goals so far, and would love to see a cleanup.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 10 05:22:52 2005

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.