public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: overseers@sourceware.org, libc-alpha@sourceware.org
Subject: Re: Early blind copy for libc-alpha
Date: Wed, 29 Apr 2020 12:25:22 -0400	[thread overview]
Message-ID: <20200429162522.GA9508@cgf.cx> (raw)
In-Reply-To: <87h7x2bc3l.fsf@mid.deneb.enyo.de>

[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]

On Wed, Apr 29, 2020 at 04:28:14PM +0200, Florian Weimer wrote:
>* Christopher Faylor:
>> On Wed, Apr 29, 2020 at 11:23:05AM +0200, Florian Weimer wrote:
>>>Would it be possible to get an early copy of messages sent to
>>><libc-alpha@sourceware.org> before they go into Mailman?
>>>
>>>It will help those of us who apply patches on other people's behalf,
>>>without having to undo the Mailman mangling first.
>>
>> What specifically is mailman doing to the email you receive?
>
>The From: header contains the list address, not the patch author,
>so feeding the message into “git am” produces an incorrect commit.

I just did a google search for "git am" "dmarc" and see that this pain
point has been around since DMARC started becoming popular.  I didn't
see any solution.  It was interesting to see people like John Levine and
Theorore T'so weighing in on the issue though.

Attached is a simple script which will rewrite the headers so that From:
is no longer munged.  I assume that this could be used as a front-end
for "git am".  This relies on the fact that we have mailman set up to
Cc: the original email sender when the address is munged.

I'm providing this as-is after 15 minutes of work.  There are probably
more elegant ways to accomplish the same task but at least the script is
short.

[-- Attachment #2: undmarc --]
[-- Type: text/plain, Size: 340 bytes --]

#!/bin/sh
t=/tmp/$$.eml
cat > $t
# e.g., From: Christopher Faylor via Test-list <test-list@sourceware.org>
from=$(sed -nre 's/^From: (.*) via .* <.*$/\1/p' $t)
# e.g., Cc: Christopher Faylor <me.test-list@cgf.cx>
cc=$(sed -nre "s/^Cc: ($from "'<.*>).*$/\1/ip' $t)
exec < $t
rm $t
exec sed -e "s/^From:.*/From: $cc/" -e "/[Cc][cC]: $cc.*/d"

      reply	other threads:[~2020-04-29 16:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29  9:23 Florian Weimer
2020-04-29 10:04 ` Frank Ch. Eigler
2020-04-29 10:13   ` Florian Weimer
2020-04-29 14:24 ` Christopher Faylor
2020-04-29 14:28   ` Florian Weimer
2020-04-29 16:25     ` Christopher Faylor [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=20200429162522.GA9508@cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=fw@deneb.enyo.de \
    --cc=libc-alpha@sourceware.org \
    --cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).