git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
YDYann Dirson <ydirson@free.fr>
Date
Jan 16, 2011, 20:56 UTC
Message-ID
<20110116205619.GR3296@home.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.
Message 1 of 1 in “[BUG] blame -M not finding that some lines were moved”
  1. Yann DirsonJan 16, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.