From: mkoegler@auto.tuwien.ac.at (Martin Koegler)
To: git@vger.kernel.org
Subject: Wrong Git rename detection results
Date: Sat, 15 Dec 2007 22:14:25 +0100 [thread overview]
Message-ID: <20071215211425.GA12334@auto.tuwien.ac.at> (raw)
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).
reply other threads:[~2007-12-15 21:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071215211425.GA12334@auto.tuwien.ac.at \
--to=mkoegler@auto.tuwien.ac.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).