Wrong Git rename detection results

Wrong Git rename detection results

[Martin Koegler]

I have reworked parts of my bcusdk repository in a separate branch
(6d102933f620b81b4a2c09046ec529460bd0c90f), which I merged into master
(9068de13cb408babf4206aa5ee55a7f8094f4ff3).

I'm interessed in the resulting differenced of the merge:
http://repo.or.cz/w/bcusdk.git?a=commitdiff;h=9068de13cb408babf4206aa5ee55a7f8094f4ff3;hp=6d102933f620b81b4a2c09046ec529460bd0c90f

The output of git is totally absurd. It tells me, that I moved a C
file to a java file with about 70% similarity, many other C files
where copied from one C file with 70% to 80% similarity, misses an
move with new lines added (eibd/client/eibclient-int.h =>
eibd/client/c/eibclient-int.h) and so on.

Additionally, it states, that files were moved to unrelated files, eg:

  eibd/client/def/mcprogmodeoff.inc [moved from eibd/client/openvbusmonitor.c with 60% similarity]

In this case, eibd/client/mcprogmodeoff.def would have been the
correct logical successor.

With git 1.5.4.rc0.1122.g5512, the rename detection yields to slightly different
results, which are also not correct.

I guess, that the problem is triggered by the fact all files
are short and share a common (big) license header.

mfg Martin Kögler
PS:
I don't doubt, that the results are technical correct (files have the
printed similarity).