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

BUG: git log --follow always follows copies as well as renames

From
GUGrochowalski, Matthew (GE Aerospace, US) <matthews.grochowalski@ge.com>
Date
Dec 1, 2022, 20:41 UTC
Message-ID
<604700f9e2e74d0db047a47c0b58ce8a@ge.com>
Encountered on git 2.38.1.143.g1fc3c0ad40
Run git log --follow -M100% --no-find-copies --name-status path/to/renamed/file
The log follows copies despite being explicitly told not to.
This apparently goes back to at least 2017; see https://stackoverflow.com/questions/44083806/how-to-prevent-git-log-follow-from-following-copies-but-only-follow-renames
--Matt Grochowalski
Message 1 of 1 in “BUG: git log --follow always follows copies as well as renames”
  1. Grochowalski, Matthew (GE Aerospace, US)Dec 1, 2022

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.