Hi,
When using -M with a number to act as a threshold for declaring
a change as being a rename, I found a... quirk. Any 2-digit
number after the M will work, but if the number is 100, it will
require a % to be appended to be effective.
Here's a transcript that will demonstrate the problem when run
in an empty directory.
# setup
git init
seq 1 100 > f1
git add f1
git commit -m f1
git rm f1
( seq 1 45; seq 1001 1010; seq 56 100 ) > f2
git add f2
git commit -m f2
# here's the buglet
git log -1 --stat --raw -M
# this tells you the files are 83% similar
git log -1 --stat --raw -M82
# this shows it like a rename
git log -1 --stat --raw -M83
# this also
git log -1 --stat --raw -M84
# this shows two separate files
git log -1 --stat --raw -M99
# this also
# so far so good...
git log -1 --stat --raw -M100
# but this shows it like a rename
git log -1 --stat --raw -M100%
# adding a percent sign fixes it, now they're two separate
# files. It seems to be required only when you ask for 100%
--
Sitaram Chamarty
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
