On 13 Sep 2009, at 20:14, Junio C Hamano wrote:
% mv file1.txt file3.txt
% mv file2.txt file1.txt
% mv file3.txt file2.txt
% git add file1.txt file2.txt
% git diff -M --stat --cached
file1.txt | 150 ++++++++++++++++++++++
+-------------------------------------
file2.txt | 150 ++++++++++++++++++++++++++++++++++++
+-----------------------
2 files changed, 150 insertions(+), 150 deletions(-)
By default, if the pathname that was present in the old version still
appears in the new version, that path is not considered as a candiate
for rename detection. Only "X used to be there but is gone" and "Y
did
not exist but appeared" are paired up and checked if they are similar.
Give the command -B option, too, to break the filepair that does not
disappear.
That does the trick. I'm curious, is there any other use for -B
besides rename handling?
Any reason of why it isn't a default when --find-copies-harder is in
effect?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html