{"thread":{"id":"26290","subject":"[BUG] blame -M not finding that some lines were moved","startedAt":"2011-01-16T20:56:19Z","lastAt":"2011-01-16T20:56:19Z","messageCount":1,"participants":["Yann Dirson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"159550","messageId":"20110116205619.GR3296@home.lan","threadId":"26290","inReplyTo":null,"subject":"[BUG] blame -M not finding that some lines were moved","fromName":"Yann Dirson","fromEmail":"ydirson@free.fr","sentAt":"2011-01-16T20:56:19Z","receivedAt":"2011-01-16T20:56:19Z","isPatch":false,"sender":{"key":"ydirson@free.fr","avatar":null},"body":"I just noticed a case where \"git blame -M\" ran on a file containing\nonly line reorderings in the last commit would still report some files\nas being introduced in the reordering commit.  Reproduced with Debian\nsqueeze's 1.7.2.3, as well as with 1.7.4.rc2.\n\nSample case is available from https://alioth.debian.org/anonscm/git/omaha/omaha.git,\ncommit 369b92da.\n\n\"git blame -L325,354 -M 369b92da README\" shows the reordered lines,\nwhere lies 332, 333, 338 are reported new in this commit.\n\nIt does not seem to be related to the -M threshold.\n"}]}