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

RE: Understanding behavior of git blame -M

From
SESokolov, Konstantin (ext) <konstantin.sokolov.ext@siemens.com>
Date
Aug 18, 2014, 11:41 UTC
Message-ID
<71BF70CE41AEE741896AF3A5450D86F11F28C80E@DEFTHW99EH3MSX.ww902.siemens.net>
In-Reply-To
<xmqq7g291y21.fsf@gitster.dls.corp.google.com>
Seems like not detecting single line movements is per design and just the documentation is not precise about this. Could such an enhancement be considered as a feature request? We're using git (blame) as a low level tool for building further functionality on top of it. Maintaining a custom version of git is a big step that we would like to avoid.

Regards Konstantin

Previous: Sokolov, Konstantin (ext)
Message 8 of 8 in “Understanding behavior of git blame -M”
  1. Sokolov, Konstantin (ext)Aug 15, 2014
  2. David KastrupAug 15, 2014
  3. AW: Understanding behavior of git blame -MSokolov, Konstantin (ext), Aug 15, 2014
  4. David KastrupAug 16, 2014
  5. Duy NguyenAug 16, 2014
  6. Junio C HamanoAug 15, 2014
  7. AW: Understanding behavior of git blame -MSokolov, Konstantin (ext), Aug 15, 2014
  8. Sokolov, Konstantin (ext)Aug 18, 2014

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.