* [BUG] blame -M not finding that some lines were moved
@ 2011-01-16 20:56 Yann Dirson
0 siblings, 0 replies; only message in thread
From: Yann Dirson @ 2011-01-16 20:56 UTC (permalink / raw)
To: GIT list
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-01-16 20:56 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-16 20:56 [BUG] blame -M not finding that some lines were moved Yann Dirson
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).