From: Yann Dirson <ydirson@free.fr>
To: GIT list <git@vger.kernel.org>
Subject: [BUG] blame -M not finding that some lines were moved
Date: Sun, 16 Jan 2011 21:56:19 +0100 [thread overview]
Message-ID: <20110116205619.GR3296@home.lan> (raw)
I just noticed a case where "git blame -M" ran on a file containing
only line reorderings in the last commit would still report some files
as being introduced in the reordering commit. Reproduced with Debian
squeeze's 1.7.2.3, as well as with 1.7.4.rc2.
Sample case is available from https://alioth.debian.org/anonscm/git/omaha/omaha.git,
commit 369b92da.
"git blame -L325,354 -M 369b92da README" shows the reordered lines,
where lies 332, 333, 338 are reported new in this commit.
It does not seem to be related to the -M threshold.
reply other threads:[~2011-01-16 20:56 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=20110116205619.GR3296@home.lan \
--to=ydirson@free.fr \
--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).