git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] parser: Unmangle From: headers that have been mangled for DMARC purposes

From
DADaniel Axtens <dja@axtens.net>
Date
Oct 11, 2019, 15:42 UTC
Message-ID
<87pnj3thja.fsf@dja-thinkpad.axtens.net>
In-Reply-To
<06541640-7eca-bc40-5c4b-9aa682d774a8@linux.ibm.com>
Hi,
Show 18 quoted lines
>> Neat. There was discussion on a similar issue recently in:
>> 
>>    https://public-inbox.org/git/305577c2-709a-b632-4056-6582771176ac@redhat.com/
>> 
>> where a possible solution was to get senders to use in-body From
>> headers even when sending their own patches.
>
> I think that's a good idea.
>
>> 
>> This might provide an alternate solution (or vice versa). I kind of like
>> this one better in that it doesn't require the sender to do anything
>> differently (but it may be less robust, as it assumes the receiver
>> reliably de-mangling).
>
> Yep, it's less robust - but OTOH there's always a long tail of users 
> stuck on old versions of git for whatever reason and having some logic 
> to detect DMARC munging may thus still be useful.
I'm not sure this solution is correct.

If I take a patch from Andrew, backport it, and send to the list, Andrew will be listed in the in-body From. However, he shouldn't be the sender from the Patchwork point of view: he shouldn't get the patch status notification emails - I should. We don't want to spam an original author if their patch is backported to several different releases, or picked up and resent in someone else's series, etc etc. So unless I've misunderstood something, we can't rely on the in-body from matching Patchwork's understanding of the sender.

Regards, Daniel

Show 9 quoted lines
>
> -- 
> Andrew Donnellan              OzLabs, ADL Canberra
> ajd@linux.ibm.com             IBM Australia Limited
>
> _______________________________________________
> Patchwork mailing list
> Patchwork@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/patchwork
Previous: Jeff KingNext: Jeff King
Message 8 of 15 in “Re: [PATCH] parser: Unmangle From: headers that have been mangled for DMARC purposes”
  1. Jonathan NiederOct 10, 2019
  2. Andrew DonnellanOct 10, 2019
  3. Daniel AxtensOct 10, 2019
  4. Stephen RothwellOct 10, 2019
  5. Jeff KingOct 10, 2019
  6. Andrew DonnellanOct 10, 2019
  7. Jeff KingOct 10, 2019
  8. Daniel AxtensOct 11, 2019
  9. Jeff KingOct 11, 2019
  10. Andrew DonnellanOct 13, 2019
  11. Junio C HamanoOct 11, 2019
  12. Andrew DonnellanOct 11, 2019
  13. Andrew DonnellanOct 11, 2019
  14. Christian SchoenebeckOct 11, 2019
  15. Ian KellingOct 11, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.