From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elastic.org (unknown [IPv6:2600:3c03::f03c:91ff:fe50:73f]) by sourceware.org (Postfix) with ESMTPS id 858613877018 for ; Mon, 16 Mar 2020 13:06:55 +0000 (GMT) Received: from vpn-home.elastic.org ([10.0.0.2] helo=elastic.org) by elastic.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jDpSJ-0000zo-9R; Mon, 16 Mar 2020 13:06:55 +0000 Received: from fche by elastic.org with local (Exim 4.92.3) (envelope-from ) id 1jDpSJ-0003h4-04; Mon, 16 Mar 2020 09:06:55 -0400 Date: Mon, 16 Mar 2020 09:06:54 -0400 From: "Frank Ch. Eigler" To: Overseers mailing list Cc: Mark Wielaard , Matthias Maennich Subject: Re: list From mangling and git am Message-ID: <20200316130654.GK79471@elastic.org> References: <20200316121624.GC39901@wildebeest.org> <20200316123210.GC211970@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200316123210.GC211970@google.com> X-Sender-Verification: "" X-Spam-Status: No, score=-96.9 required=5.0 tests=DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_SBL_CSS, SPF_HELO_PASS, SPF_PASS, USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2020 13:06:56 -0000 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