From: Taylor Blau <me@ttaylorr.com>
To: "L. E. Segovia" <amy@amyspark.me>
Cc: Taylor Blau <me@ttaylorr.com>, git@vger.kernel.org
Subject: Re: [BUG] git format-patch incorrectly follows the mailmap when used with --cover-letter
Date: Wed, 2 Nov 2022 20:26:23 -0400 [thread overview]
Message-ID: <Y2MKr2Yga/o1sjun@nand.local> (raw)
In-Reply-To: <527f8050-7955-50b1-304c-617703cf99e6@amyspark.me>
On Wed, Nov 02, 2022 at 09:21:12PM -0300, L. E. Segovia wrote:
> Hey,
>
> The shortlog in the cover letter follows the active mailmap (incorrectly).
You say "incorrectly", but this is subjective, no?
I imagine that most (?) users of format-patch do want to respect the
mailmap when generating a shortlog. In fact, the 'git shortlog' builtin
doesn't even have a `--[no-]mailmap` option, either.
> The letter itself (From: header), as well as the patches, are attributed
> correctly.
OK.
Thanks,
Taylor
prev parent reply other threads:[~2022-11-03 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 23:54 [BUG] git format-patch incorrectly follows the mailmap when used with --cover-letter L. E. Segovia
2022-11-03 0:09 ` Taylor Blau
2022-11-03 0:21 ` L. E. Segovia
2022-11-03 0:26 ` Taylor Blau [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y2MKr2Yga/o1sjun@nand.local \
--to=me@ttaylorr.com \
--cc=amy@amyspark.me \
--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.
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 NNTP newsgroup(s).