On Fri, 20 May 2005 kfogel@collab.net wrote:
> "Peter N. Lundblad" <peter@famlundblad.se> writes:
> > Sounds perfectly reasonable. So, let's handle purely added files and
> > copies separately. We have --no-diffs-added for the former; that will
> > either ahve added files diffed against the empty file or no diffs at all.
> > The latter would be handled by a switch to use diffs against the copy
> > source instead of the empty stream. I don't think we need to be able to
> > turn off diffs for copied files entirely. So, any suggestions for names
> > for the new option? --diff-copied-against-source? (A little long.)
>
> I think diffing copied files against the source should be the default
> behavior. The option could be '--diff-copies-as-adds'?
>
This is inconsitent with svn diff, and, worse, it makes it impossible to
push those diffs through patch, which doesn't know about our revisions, of
coruse. I guess that's why svn diff behaves like it does, but as I pointed
out in another mail, that's inconsistent in itself. svn diff (WC against
base) will give copies-against-source, but diffing URLs will give
copies-against-empty-file.
But maybe svnlook is more for creating diffs to be read by humans. IN that
case, I like your suggestion. Else, I guess --no-diff-copies-as-adds is
the way to go.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 22 22:10:06 2005