{"thread":{"id":"58885","subject":"BUG: git log --follow always follows copies as well as renames","startedAt":"2022-12-01T21:43:33Z","lastAt":"2022-12-01T21:43:33Z","messageCount":1,"participants":["Grochowalski, Matthew (GE Aerospace, US)"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"468355","messageId":"604700f9e2e74d0db047a47c0b58ce8a@ge.com","threadId":"58885","inReplyTo":null,"subject":"BUG: git log --follow always follows copies as well as renames","fromName":"Grochowalski, Matthew (GE Aerospace, US)","fromEmail":"matthews.grochowalski@ge.com","sentAt":"2022-12-01T20:41:22Z","receivedAt":"2022-12-01T21:43:33Z","isPatch":false,"sender":{"key":"matthews.grochowalski@ge.com","avatar":null},"body":"Encountered on git 2.38.1.143.g1fc3c0ad40\n\nRun git log --follow -M100% --no-find-copies --name-status path/to/renamed/file\n\nThe log follows copies despite being explicitly told not to.\n\nThis 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\n\n--Matt Grochowalski\n"}]}