[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: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-10-10 09:16:38 CEST

On Sun, 9 Oct 2005, Ben Collins-Sussman wrote:

> 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
> folly.
Just for the record, in 1.3, svnlook diff got a --dif-copy-from option.
The default is to show added files as diffs against the empty stream, and
this option making it show what svn diff BASE:WORKING does today. To me,
it is reasonable that the default behaviour should be a format tha patch
can read. I don't know what compatibility problem we might cause if we
make this behaviour consistent across svn diff...


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 10 09:19:08 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.