# [BUG] blame -M not finding that some lines were moved

1 messages from 2011-01-16 to 2011-01-16. Participants: Yann Dirson.
Thread: https://gitlist.dev/t/26290

## Yann Dirson, 2011-01-16 20:56

Subject: [BUG] blame -M not finding that some lines were moved
Message-ID: <20110116205619.GR3296@home.lan>
URL: https://gitlist.dev/e/20110116205619.GR3296%40home.lan

```
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.

```