interesting that it considers suffixes {only suffixes following
periods?}. this is insufficient, in my opinion.
with all other things being equal, it ought to find the closest match
{using smith-waterman or some such algorithm}.
as a real-world use case, i have a repository with empty files that
mirrors the file structure of a directory containing large binary files.
when i move a dir, it seems to select the files renamed at random.
On 07/01/2014 05:16 AM, Robin Rosenberg wrote:
----- Ursprungligt meddelande -----
Från: "Elliot Wolk" <elliot.w...@gmail.com>
Till: git@vger.kernel.org
Skickat: måndag, 30 jun 2014 8:38:18
Ämne: move detection doesnt take filename into account
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.
I think it does, but based on filename suffix. E.g. here is a rename of
three empty files with a suffix.
3 files changed, 0 insertions(+), 0 deletions(-)
rename 1.a => 2.a (100%)
rename 1.b => 2.b (100%)
rename 1.c => 2.c (100%)
-- robin
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
