From: Elliot Wolk <elliot.wolk@gmail.com>
To: git@vger.kernel.org
Subject: move detection doesnt take filename into account
Date: Mon, 30 Jun 2014 02:38:18 -0400 [thread overview]
Message-ID: <53B105DA.30004@gmail.com> (raw)
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@gmail.com>
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@gmail.com>
Date: Mon Jun 30 02:26:49 2014 -0400
1
A a1
A b1
A c1
next reply other threads:[~2014-06-30 6:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 6:38 Elliot Wolk [this message]
2014-07-01 9:16 ` move detection doesnt take filename into account Robin Rosenberg
2014-07-01 14:40 ` Elliot Wolk
2014-07-01 14:57 ` Junio C Hamano
2014-07-01 15:05 ` Elliot Wolk
2014-07-01 17:08 ` Junio C Hamano
2014-07-09 6:45 ` Jeff King
2014-07-09 15:51 ` Junio C Hamano
2014-07-09 22:03 ` Jeff King
2014-07-09 22:18 ` Junio C Hamano
2014-07-10 3:53 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53B105DA.30004@gmail.com \
--to=elliot.wolk@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.