list From mangling and git am

Frank Ch. Eigler fche@elastic.org
Mon Mar 16 13:06:54 GMT 2020


Hi -

> > The mailinglist From/Reply-To mangling doesn't interact nicely with
> > git am. [...]

As you know, increasing mail security/spam measures are what is
driving cleanliness with respect to mailing list systems.  Even as we
speak, we have outgoing email from sourceware to important receivers
like gmail -blocked- because the receiver doesn't think we are clean
enough.  So I suspect we'll need to retain/enhance these measures
rather than roll them back.

For git am workflows, consider:

- running "git amend --author=<....>" after "git am" to fix things

- asking submitters to use "git format-patch --from="Real Name git <...>"
  where the enclosed name is different enough that git format-patch
  includes a second From: header in the body, which git-am prefers

- using the mailing list mbox (which has the received form of emails
  rather than the retransmitted ones) as patch source

And also:

- using git branches / bugzilla / other systems, which do not rely
  on mailing list header preservation

- adding patches as attachments (so not plain git send-email)


- FChE


More information about the Overseers mailing list