From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 105324 invoked by alias); 11 Dec 2019 15:21:18 -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 105314 invoked by uid 89); 11 Dec 2019 15:21:17 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=H*f:sk:CAH6eHd, H*i:sk:CAH6eHd, H*i:Mu5, H*i:sk:Ctni783 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; Wed, 11 Dec 2019 15:21:16 +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 5D62D30E; Wed, 11 Dec 2019 07:21:15 -0800 (PST) Received: from [192.168.1.19] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 6A5AE3F52E; Wed, 11 Dec 2019 07:21:14 -0800 (PST) Subject: Re: Proposal for the transition timetable for the move to GIT To: Jonathan Wakely Cc: Maxim Kuvyrkov , "Joseph S. Myers" , "Eric S. Raymond" , Richard Guenther , "gcc@gcc.gnu.org" References: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> <9E009921-96EA-44A2-A06A-232711227E69@linaro.org> <20191206172111.GA116282@thyrsus.com> <0485C474-1B83-42C2-AEAD-7CA252C6CC12@gmail.com> <20191206194604.GA115432@thyrsus.com> <9C7E86D4-AFDE-4EFB-B804-A03C99042B3E@linaro.org> <8d18e5ca-584c-bec7-c429-b6cc416c78c7@arm.com> From: "Richard Earnshaw (lists)" Message-ID: Date: Wed, 11 Dec 2019 15:21: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: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-12/txt/msg00170.txt.bz2 On 11/12/2019 15:19, Jonathan Wakely wrote: > On Wed, 11 Dec 2019 at 15:03, Richard Earnshaw (lists) wrote: >> I wouldn't bother with that. There are known defects in the version of >> reposurgeon that I used to produce that which have since been fixed. It >> was *never* the point of that upload to ask for correctness checks on >> the conversion (I said so at the time). Instead it was intended to >> demonstrate the improvements to the commit summaries that I think we can >> make. > > My concern is that there is no conversion done using reposurgeon that > *can* be used to do correctness checks. > I have concerns too, but I'm in contact with the reposurgeon guys and progress *is* being made. R.