public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>, Matthias Maennich <maennich@google.com>
Subject: Re: list From mangling and git am
Date: Mon, 16 Mar 2020 09:06:54 -0400	[thread overview]
Message-ID: <20200316130654.GK79471@elastic.org> (raw)
In-Reply-To: <20200316123210.GC211970@google.com>

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

  reply	other threads:[~2020-03-16 13:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 12:16 Mark Wielaard
2020-03-16 12:32 ` Matthias Maennich
2020-03-16 13:06   ` Frank Ch. Eigler [this message]
2020-03-20 18:03     ` Mark Wielaard
2020-03-22 21:15       ` Matthias Maennich

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=20200316130654.GK79471@elastic.org \
    --to=fche@elastic.org \
    --cc=maennich@google.com \
    --cc=mark@klomp.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).