Re: 1.6 vs. 1.8: strange behavior of 'svn diff -cN WC-FILE' if the file was created in rev N by copying

> > Well, I forgot about "svn log --diff -l1 new_foo".

[Tobias Bading]
> Good idea, but unfortunately no cigar.

You're right. I tested that command but somehow glazed over the fact
that it did not do what I said it did. Sorry. Anyway, parsing the
'svn log -v -l1 {filename}' output, then running 'svn diff -rM:N', is
still correct.

How do git et al. deal with the ambiguity you are presenting, anyway?
I mean, you have this file, it is present in this revision, it came
from _somewhere_ but not from the parent revision. How do you tell it
that you don't want the usual thing, a diff against the parent revision
('git show'), but instead, a diff against wherever the file came from?
Received on 2013-06-25 21:51:34 CEST