unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Sarah Morgensen <iskarian@mgsn.dev>
Cc: guix-devel@gnu.org
Subject: Re: Mailman From header rewrite
Date: Sat, 24 Jul 2021 18:00:04 -0400	[thread overview]
Message-ID: <875ywzpe3f.fsf@kyleam.com> (raw)
In-Reply-To: <86h7gstbuw.fsf@mgsn.dev>

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:

  https://lore.kernel.org/git/305577c2-709a-b632-4056-6582771176ac@redhat.com/T/#u

As a hacky/ugly way, for those that are okay tweaking the way their
names ends up on the mailing list, they can adjust `send-email --from=`
(or sendemail.from) slightly so that it doesn't match
user.name/user.email, and then send-email should take care of adding an
in-body header for user.name/user.email.

Another option is of course to feed the patches to a custom
post-processing script that adds the in-body "From:", where the details
would depend a bit on the person's patch workflow.

Or, moving that work a bit upstream, I think it'd be fairly
straightforward to wire up a prepare-commit-msg hook that would insert
an in-body "From:" (after checking some things, like whether the commit
is being amended).  I guess the main disadvantage of handling it at this
spot is the risk of commits with in-body "From:" headers unintentionally
being merged/pushed directly to the main line (given the person has
commit access).


  reply	other threads:[~2021-07-24 22:00 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 [this message]
2022-10-29 21:13               ` Kyle Meyer

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=875ywzpe3f.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=guix-devel@gnu.org \
    --cc=iskarian@mgsn.dev \
    /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).