From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.81]) by sourceware.org (Postfix) with ESMTP id 5ECF4386F023 for ; Thu, 23 Apr 2020 15:33:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5ECF4386F023 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-103-c4jENJc7MbG_8YocwA6xvw-1; Thu, 23 Apr 2020 11:33:51 -0400 X-MC-Unique: c4jENJc7MbG_8YocwA6xvw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 3F871100CCC0; Thu, 23 Apr 2020 15:33:49 +0000 (UTC) Received: from ovpn-113-172.phx2.redhat.com (ovpn-113-172.phx2.redhat.com [10.3.113.172]) by smtp.corp.redhat.com (Postfix) with ESMTP id 1DCAF10016EB; Thu, 23 Apr 2020 15:33:48 +0000 (UTC) Message-ID: Subject: Re: Not usable email content encoding From: Jeff Law Reply-To: law@redhat.com To: Segher Boessenkool , Tamar Christina Cc: "overseers@gcc.gnu.org" , Jonathan Wakely via Gcc , Overseers mailing list , Alexander Monakov , "Frank Ch. Eigler" , "Frank Ch. Eigler" , Florian Weimer , Tom Tromey Date: Thu, 23 Apr 2020 09:33:47 -0600 In-Reply-To: <20200423114627.GG26902@gate.crashing.org> References: <3af9771e-e577-f2a1-843e-c2b078bfc4ea@t-online.de> <20200318162250.GG112952@elastic.org> <87zhccsdfd.fsf@tromey.com> <87imj0pjbr.fsf@mid.deneb.enyo.de> <87blosphsw.fsf@mid.deneb.enyo.de> <20200423114627.GG26902@gate.crashing.org> Organization: Red Hat User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-10.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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: Thu, 23 Apr 2020 15:33:54 -0000 On Thu, 2020-04-23 at 06:46 -0500, Segher Boessenkool wrote: > Hi! > > On Thu, Apr 23, 2020 at 12:54:04AM +0000, Tamar Christina wrote: > > but trains for GCC Will likely be very short because of Changelog conflicts. > > Why that? Your patches should *not* touch changelog files, ever. > > For CI it is probably easiest if the CI never gets to see the changelog > at all, and that isn't hard to do ;-) *Nothing* should touch changelog files :-) They should be generated from the VCS. IMHO of course. That implies that the patch includes a proper ChangeLog entry in the commit message. It also implies that if we muck one up, then we live with it rather than going back and rewriting them. jeff