From: Kyle Meyer <kyle@kyleam.com>
To: Sarah Morgensen <iskarian@mgsn.dev>
Cc: Ryan Prior <rprior@protonmail.com>, guix-devel@gnu.org
Subject: Re: Mailman From header rewrite
Date: Sat, 29 Oct 2022 17:13:59 -0400 [thread overview]
Message-ID: <87k04ijpt4.fsf@kyleam.com> (raw)
In-Reply-To: <875ywzpe3f.fsf@kyleam.com>
Kyle Meyer writes:
> Sarah Morgensen writes:
>
>> On Tuesday, January 5th, 2021 at 5:01 AM, Kyle Meyer <kyle@kyleam.com> wrote:
>>
>>> add the appropriate "From:" header to the body of each patch. `git am`
>>> will take the in-body header over the actual header.
>>
>> I wonder if there is a way to automate the duplication of the "From"
>> header into the body of the patch?
>
> I'm not aware of an existing way at the git level. Here's the only
> discussion I found about it on the git list [...]
Git 2.38.0 gained support for this via a --force-in-body-from option and
the associated format.forceInBodyFrom config variable.
https://lore.kernel.org/git/20220829213837.13849-1-gitster@pobox.com/
prev parent reply other threads:[~2022-10-29 21:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <X/J1vu/GBTP9DKhH@jasmine.lan>
[not found] ` <20210104014732.19791-1-rprior@protonmail.com>
[not found] ` <handler.45644.D45644.160972538318518.notifdone@debbugs.gnu.org>
2021-01-04 2:47 ` [bug#45644] closed (Re: [bug#45644] [PATCH] gnu: esbuild: Update to 0.8.29.) Ryan Prior via Guix-patches via
2021-01-04 17:02 ` Tobias Geerinckx-Rice via Development of GNU Guix and the GNU System distribution.
2021-01-04 17:07 ` Tobias Geerinckx-Rice via Development of GNU Guix and the GNU System distribution.
2021-01-04 17:56 ` Leo Famulari
2021-01-05 5:01 ` Mailman From header rewrite (was: [bug#45644] closed (Re: [bug#45644] [PATCH] gnu: esbuild: Update to 0.8.29.)) Kyle Meyer
2021-01-05 5:22 ` Kyle Meyer
2021-01-05 5:35 ` Ryan Prior via Development of GNU Guix and the GNU System distribution.
2021-07-18 5:44 ` Mailman From header rewrite Sarah Morgensen
2021-07-24 22:00 ` Kyle Meyer
2022-10-29 21:13 ` Kyle Meyer [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k04ijpt4.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=guix-devel@gnu.org \
--cc=iskarian@mgsn.dev \
--cc=rprior@protonmail.com \
/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://git.savannah.gnu.org/cgit/guix.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).