From: "Michael Brown" <mcb30@ipxe.org>
To: devel@edk2.groups.io, lersek@redhat.com,
Ard Biesheuvel <ardb@kernel.org>,
Michael Kinney <michael.d.kinney@intel.com>
Cc: rebecca@os.amperecomputing.com, Jeff Brasen <jbrasen@nvidia.com>,
jake@nvidia.com, Michael.Roth@amd.com,
joeyvagedes@microsoft.com
Subject: Re: [edk2-devel] Updates to .mailmap needed for Jeff Brasen, Jake Garver, Joey Vagades and Michael Roth?
Date: Tue, 9 Jan 2024 12:28:37 +0000 [thread overview]
Message-ID: <0102018cee32359e-436bd43a-4778-462e-98a3-7d00c24eb27e-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <24565570-4147-db82-27c1-1281c895254a@redhat.com>
On 09/01/2024 12:13, Laszlo Ersek wrote:
> On 1/9/24 11:45, Ard Biesheuvel wrote:
>> Note that git am does support a 'From: ' header as the first line of
>> the commit log, and will use it correctly to supersede the From:
>> header in the SMTP envelope.
>
> OTOH, that doesn't help in this case, IIUC. When the poster originally
> formats and sends the patch, their gitconfig says
> user.email=foobar@example.com, and the author meta-datum on the patch
> most likely *also* says foobar@example.com. (I.e., they are formatting a
> patch they have authored themselves.) Therefore
> git-format-patch/git-send-email have no reason to include an explicit
> "From:" line at the top of the commit message body. I agree that
> "From:", if present, mitigates the issue, but in most cases, I reckon,
> it's not present.
Is there a way to configure git to force git-format-patch to
unconditionally include the inline "From:" header? I tried:
git config format.forceInBodyFrom true
which is described in the man page as "may help if the mailing list
software mangles the sender’s identity", but it seems to have an effect
only if "--from" is also specified.
Thanks,
Michael
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#113446): https://edk2.groups.io/g/devel/message/113446
Mute This Topic: https://groups.io/mt/103534194/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-01-09 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 0:05 [edk2-devel] Updates to .mailmap needed for Jeff Brasen, Jake Garver, Joey Vagades and Michael Roth? Rebecca Cran via groups.io
2024-01-08 15:56 ` Joey Vagedes via groups.io
2024-01-09 9:17 ` Laszlo Ersek
2024-01-09 10:45 ` Ard Biesheuvel
2024-01-09 12:13 ` Laszlo Ersek
2024-01-09 12:28 ` Michael Brown [this message]
2024-01-09 13:33 ` Laszlo Ersek
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-list 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=0102018cee32359e-436bd43a-4778-462e-98a3-7d00c24eb27e-000000@eu-west-1.amazonses.com \
--to=devel@edk2.groups.io \
/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