From: "Grochowalski, Matthew (GE Aerospace, US)" <MatthewS.Grochowalski@ge.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: BUG: git log --follow always follows copies as well as renames
Date: Thu, 1 Dec 2022 20:41:22 +0000 [thread overview]
Message-ID: <604700f9e2e74d0db047a47c0b58ce8a@ge.com> (raw)
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
reply other threads:[~2022-12-01 21:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=604700f9e2e74d0db047a47c0b58ce8a@ge.com \
--to=matthews.grochowalski@ge.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).