From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <segher@kernel.crashing.org>
Received: from gate.crashing.org (gate.crashing.org [63.228.1.57])
 by sourceware.org (Postfix) with ESMTP id 0137C385DC0B;
 Thu, 23 Apr 2020 12:30:19 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 0137C385DC0B
Received: from gate.crashing.org (localhost.localdomain [127.0.0.1])
 by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 03NCUCKL007752;
 Thu, 23 Apr 2020 07:30:12 -0500
Received: (from segher@localhost)
 by gate.crashing.org (8.14.1/8.14.1/Submit) id 03NCUA8S007751;
 Thu, 23 Apr 2020 07:30:10 -0500
X-Authentication-Warning: gate.crashing.org: segher set sender to
 segher@kernel.crashing.org using -f
Date: Thu, 23 Apr 2020 07:30:10 -0500
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Tamar Christina <Tamar.Christina@arm.com>,
 "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>,
 Jonathan Wakely via Gcc <gcc@gcc.gnu.org>,
 Overseers mailing list <overseers@sourceware.org>,
 Alexander Monakov <amonakov@ispras.ru>,
 "Frank Ch. Eigler" <fche@elastic.org>,
 "Frank Ch. Eigler" <fche@redhat.com>,
 Florian Weimer <fw@deneb.enyo.de>, Tom Tromey <tom@tromey.com>
Subject: Re: Not usable email content encoding
Message-ID: <20200423123010.GK26902@gate.crashing.org>
References: <alpine.LSU.2.21.2003181638490.30534@wotan.suse.de>
 <CAFyWVaZfY-CfXwsTwrF8LduSBMYdFecD3x7MLP0ZYb8pC5qZPA@mail.gmail.com>
 <CAH6eHdQe5PdRe42BFeN4e9Ms9jy5Lb2R==FxENbD1TWnefnekA@mail.gmail.com>
 <87zhccsdfd.fsf@tromey.com> <87imj0pjbr.fsf@mid.deneb.enyo.de>
 <CAFiYyc1q6wBHOfCu2tuPj+bXCQyLfmve0iACVYZghve2GMfoaQ@mail.gmail.com>
 <87blosphsw.fsf@mid.deneb.enyo.de>
 <PR2PR08MB47473ECD0B20FFC0D2EF576BFFD30@PR2PR08MB4747.eurprd08.prod.outlook.com>
 <20200423114627.GG26902@gate.crashing.org>
 <CAH6eHdTHsZWO9vuycKm22dDbSGSfzcrKbzEpb6vNdb-zXCiKjQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAH6eHdTHsZWO9vuycKm22dDbSGSfzcrKbzEpb6vNdb-zXCiKjQ@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-Spam-Status: No, score=-11.5 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
 KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, TXREP, T_SPF_HELO_PERMERROR,
 T_SPF_PERMERROR 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 <overseers.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/overseers>,
 <mailto:overseers-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/overseers>,
 <mailto:overseers-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2020 12:30:20 -0000

On Thu, Apr 23, 2020 at 12:56:20PM +0100, Jonathan Wakely wrote:
> On Thu, 23 Apr 2020 at 12:47, Segher Boessenkool
> <segher@kernel.crashing.org> wrote:
> > 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 ;-)
> 
> For the actual CI testing, yes. But if you want an automated "merge
> after CI testing passes" then what you merge needs to add a ChangeLog
> entry. So either we auto-generate the entry when doing the auto-merge,
> or the ChangeLog entry is already there.

Why would we make it part of the patch for that?  That is backwards :-)

If it isn't part of the patch, no matter how we do it I don't see how
it would cause conflicts?


Segher