From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-200951-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 100885 invoked by alias); 11 Dec 2019 15:19:30 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 100868 invoked by uid 89); 11 Dec 2019 15:19:29 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=earnshaw, H*i:sk:8d18e5c, Earnshaw, H*f:sk:8d18e5c
X-HELO: mail-wm1-f43.google.com
Received: from mail-wm1-f43.google.com (HELO mail-wm1-f43.google.com) (209.85.128.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 11 Dec 2019 15:19:28 +0000
Received: by mail-wm1-f43.google.com with SMTP id p17so3035546wmb.0        for <gcc@gcc.gnu.org>; Wed, 11 Dec 2019 07:19:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc;        bh=ohlUnnmEnGIAC8wEPk6cyTFSxd+adXo8Wbx7qsjl7/U=;        b=q3QDP58K+Mfcdcm9ggiMeIY9hNlQYnTaWwDtZp1ibfTZvdleP5w+5Iw1NDUFNiRtkD         vijm6C4r8PRAz2AbBvzb6x1L88O4XOCgMM6GtKDYH4pyxuWQCPOUVZdCby9jNd74kPbS         NoqfR+IXV2myYQzh7lhteMBS5KLO8VYevAk0FdpxL50O06LfFUJ3T+/1WLSoYS3oZncd         V3jW4Jf16V4i63B5vlM4OG08SQhHk8PdVUaSX63b+voxxekPXpofwb98KwcEi9QMOReI         UZKNr+9nR/cBzZ+XH4GlK3C3v+w6X5xDx3M9g5OAjjXzdy98UZmrCBkCNVcaAzMuYPgE         fbOg==
MIME-Version: 1.0
References: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> <9E009921-96EA-44A2-A06A-232711227E69@linaro.org> <BEB3D1BD-86C3-4B1A-A1BB-62461A7DCAD8@linaro.org> <20191206172111.GA116282@thyrsus.com> <0485C474-1B83-42C2-AEAD-7CA252C6CC12@gmail.com> <20191206194604.GA115432@thyrsus.com> <alpine.DEB.2.21.1912091742310.26329@digraph.polyomino.org.uk> <9C7E86D4-AFDE-4EFB-B804-A03C99042B3E@linaro.org> <8d18e5ca-584c-bec7-c429-b6cc416c78c7@arm.com>
In-Reply-To: <8d18e5ca-584c-bec7-c429-b6cc416c78c7@arm.com>
From: Jonathan Wakely <jwakely.gcc@gmail.com>
Date: Wed, 11 Dec 2019 15:19:00 -0000
Message-ID: <CAH6eHdTq4EhfwvJ_mh19djrtLhvVgzh+Mu5=Ctni783z_WOgnA@mail.gmail.com>
Subject: Re: Proposal for the transition timetable for the move to GIT
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
Cc: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>, "Joseph S. Myers" <joseph@codesourcery.com>, 	"Eric S. Raymond" <esr@thyrsus.com>, Richard Guenther <richard.guenther@gmail.com>, 	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2019-12/txt/msg00169.txt.bz2

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.