if you move two identical {e.g.: empty} files to two new locations in a
single commit, the move detection picks them {seemingly?} arbitrarily.
it should use a statistical algorithm to compare the filenames and pick
a likely match.
my apologies in advance if this isnt the right venue or is improperly
formatted, or if this is extraneous noise, or widely known, etc.
+ cd /tmp
+ mkdir repo
+ cd repo
+ git init
Initialized empty Git repository in /tmp/repo/.git/
+ touch a1 b1 c1
+ git add a1 b1 c1
+ git commit -m 1
[master (root-commit) 72f8c89] 1
3 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 a1
create mode 100644 b1
create mode 100644 c1
+ git mv a1 a2
+ git mv b1 b2
+ git mv c1 c2
+ git commit -m 2
[master 359da78] 2
3 files changed, 0 insertions(+), 0 deletions(-)
rename c1 => a2 (100%)
rename b1 => b2 (100%)
rename a1 => c2 (100%)
+ git log --name-status -M
commit 359da78caaaf06848ae32359abfeb87db35cdb30
Author: Elliot Wolk <elliot.wolk@xxxxxxxxx>
Date: Mon Jun 30 02:26:49 2014 -0400
2
R100 c1 a2
R100 b1 b2
R100 a1 c2
commit 72f8c89b418e3b1d13ec350f4c30b5088fc69e83
Author: Elliot Wolk <elliot.wolk@xxxxxxxxx>
Date: Mon Jun 30 02:26:49 2014 -0400
1
A a1
A b1
A c1
--
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