From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 99741 invoked by alias); 19 Dec 2019 16:03:36 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 99730 invoked by uid 89); 19 Dec 2019 16:03:35 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=handed X-HELO: foss.arm.com Received: from foss.arm.com (HELO foss.arm.com) (217.140.110.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 19 Dec 2019 16:03:34 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 9668F1FB; Thu, 19 Dec 2019 08:03:32 -0800 (PST) Received: from e120077-lin.cambridge.arm.com (e120077-lin.cambridge.arm.com [10.2.78.81]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id E4F463F718; Thu, 19 Dec 2019 08:03:31 -0800 (PST) Subject: Re: Test GCC conversions (publicly) available To: esr@thyrsus.com, Joseph Myers Cc: Mark Wielaard , gcc@gcc.gnu.org References: <20191219140609.GC38517@thyrsus.com> <20191219160041.GA94124@thyrsus.com> From: "Richard Earnshaw (lists)" Message-ID: <9cfe20d9-0609-2208-b779-a97a20e0a890@arm.com> Date: Thu, 19 Dec 2019 16:03:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20191219160041.GA94124@thyrsus.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2019-12/txt/msg00327.txt.bz2 On 19/12/2019 16:00, Eric S. Raymond wrote: > Joseph Myers : >> On Thu, 19 Dec 2019, Eric S. Raymond wrote: >> >>> There are other problems that might cause a delay beyond the >>> 31st, however. Best if I let Joseph nd Richard explain those. >> >> I presume that's referring to the checkme: bug annotations where the PR >> numbers in commit messages seem suspicious. I don't think that's >> something to delay the conversion unless we're clearly close to having a >> complete review of all those cases done; at the point of the final >> conversion we should simply change the script not to modify commit >> messages in any remaining unresolved suspicious cases. > > No, I was thinking more of rearnsha bailing out to handle a family emergency > and muttering something about not being back for a couple of weeks. If that's > been resolved I haven't heard about it. I don't think that should affect things, as I think Joseph has a good handle on what needs to be done and I think I've handed over everything that's needed w.r.t. the commit summary reprocessing script. Joseph, holler quickly if you think there's anything else you might need... R.