* Early blind copy for libc-alpha
@ 2020-04-29 9:23 Florian Weimer
2020-04-29 10:04 ` Frank Ch. Eigler
2020-04-29 14:24 ` Christopher Faylor
0 siblings, 2 replies; 6+ messages in thread
From: Florian Weimer @ 2020-04-29 9:23 UTC (permalink / raw)
To: overseers; +Cc: libc-alpha
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.
I would manage bounce processing etc. myself for that alternative
alias, on none-sourceware infrastructure.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Early blind copy for libc-alpha
2020-04-29 9:23 Early blind copy for libc-alpha Florian Weimer
@ 2020-04-29 10:04 ` Frank Ch. Eigler
2020-04-29 10:13 ` Florian Weimer
2020-04-29 14:24 ` Christopher Faylor
1 sibling, 1 reply; 6+ messages in thread
From: Frank Ch. Eigler @ 2020-04-29 10:04 UTC (permalink / raw)
To: Overseers mailing list; +Cc: Florian Weimer, libc-alpha
Hi -
> Would it be possible to get an early copy of messages sent to
> <libc-alpha@sourceware.org> before they go into Mailman?
The closest thing I can think of is adding a new alias, like
libc-alpha-raw, which expands to libc-alpha and you?
> It will help those of us who apply patches on other people's behalf,
> without having to undo the Mailman mangling first.
Please also see alternatives outlined in:
https://sourceware.org/pipermail/overseers/2020q1/016783.html
- FChE
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Early blind copy for libc-alpha
2020-04-29 10:04 ` Frank Ch. Eigler
@ 2020-04-29 10:13 ` Florian Weimer
0 siblings, 0 replies; 6+ messages in thread
From: Florian Weimer @ 2020-04-29 10:13 UTC (permalink / raw)
To: Frank Ch. Eigler; +Cc: Overseers mailing list, libc-alpha
* Frank Ch. Eigler:
>> Would it be possible to get an early copy of messages sent to
>> <libc-alpha@sourceware.org> before they go into Mailman?
>
> The closest thing I can think of is adding a new alias, like
> libc-alpha-raw, which expands to libc-alpha and you?
Thanks. No, that's not really useful, sorry.
>> It will help those of us who apply patches on other people's behalf,
>> without having to undo the Mailman mangling first.
>
> Please also see alternatives outlined in:
> https://sourceware.org/pipermail/overseers/2020q1/016783.html
I guess moving glibc development to a platform that does not have this
problem is something we have to consider at this point. I do not
think adding even more requirements for contributors is the
appropriate way forward.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Early blind copy for libc-alpha
2020-04-29 9:23 Early blind copy for libc-alpha Florian Weimer
2020-04-29 10:04 ` Frank Ch. Eigler
@ 2020-04-29 14:24 ` Christopher Faylor
2020-04-29 14:28 ` Florian Weimer
1 sibling, 1 reply; 6+ messages in thread
From: Christopher Faylor @ 2020-04-29 14:24 UTC (permalink / raw)
To: Florian Weimer; +Cc: overseers, libc-alpha
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?
cgf
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Early blind copy for libc-alpha
2020-04-29 14:24 ` Christopher Faylor
@ 2020-04-29 14:28 ` Florian Weimer
2020-04-29 16:25 ` Christopher Faylor
0 siblings, 1 reply; 6+ messages in thread
From: Florian Weimer @ 2020-04-29 14:28 UTC (permalink / raw)
To: overseers; +Cc: libc-alpha
* 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Early blind copy for libc-alpha
2020-04-29 14:28 ` Florian Weimer
@ 2020-04-29 16:25 ` Christopher Faylor
0 siblings, 0 replies; 6+ messages in thread
From: Christopher Faylor @ 2020-04-29 16:25 UTC (permalink / raw)
To: Florian Weimer; +Cc: overseers, libc-alpha
[-- 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"
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-04-29 16:25 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-29 9:23 Early blind copy for libc-alpha 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 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).