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 56D153945042; Wed, 18 Mar 2020 22:33:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 56D153945042 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 1jEhFN-0003bm-1D; Wed, 18 Mar 2020 22:33:09 +0000 Received: from fche by elastic.org with local (Exim 4.92.3) (envelope-from ) id 1jEhFM-0006mF-4z; Wed, 18 Mar 2020 18:33:08 -0400 Date: Wed, 18 Mar 2020 18:33:08 -0400 From: "Frank Ch. Eigler" To: Jim Wilson Cc: Michael Matz , overseers@gcc.gnu.org, "Frank Ch. Eigler via Gcc" , Overseers mailing list , Segher Boessenkool , Alexander Monakov , "Frank Ch. Eigler" , Florian Weimer Subject: Re: Not usable email content encoding Message-ID: <20200318223308.GJ112952@elastic.org> References: <20200317194613.GH22482@gate.crashing.org> <20200317195158.GC112952@elastic.org> <874kumt0bh.fsf@mid.deneb.enyo.de> <20200318110109.GA5496@redhat.com> <20200318142239.GF112952@elastic.org> <3af9771e-e577-f2a1-843e-c2b078bfc4ea@t-online.de> <20200318162250.GG112952@elastic.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Wed, 18 Mar 2020 22:33:15 -0000 Hi, Jim - > [gerrit etc.] Good points. > [...] We need to think about setting up easier ways for people to > submit patches, rather than trying to fix all of the MUAs and MTAs > in the world. Another related point. We are comingling email as a communication medium AND a commit transport medium. For the former, as in patch review / RFC, one may not require a form of the patch that is finally committable to master, so the exact From: etc. may not matter. For the latter, attachments are more bullet-proof. - FChE