* BUG: git log --follow always follows copies as well as renames
@ 2022-12-01 20:41 Grochowalski, Matthew (GE Aerospace, US)
0 siblings, 0 replies; only message in thread
From: Grochowalski, Matthew (GE Aerospace, US) @ 2022-12-01 20:41 UTC (permalink / raw)
To: git@vger.kernel.org
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-12-01 21:43 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-01 20:41 BUG: git log --follow always follows copies as well as renames Grochowalski, Matthew (GE Aerospace, US)
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).