From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 104474 invoked by alias); 16 Dec 2019 23:18:32 -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 104456 invoked by uid 89); 16 Dec 2019 23:18:31 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:1779, correspondences X-HELO: esa2.mentor.iphmx.com Received: from esa2.mentor.iphmx.com (HELO esa2.mentor.iphmx.com) (68.232.141.98) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 16 Dec 2019 23:18:30 +0000 IronPort-SDR: uC55lPdIJ3iPZVQWulg6Q9dZm+S3jheH8eOELt2fb2+IgXMINc7LK3Yxommz/mleAfQ9mtCyDd 35B23ZuDO2vMxKUgV5tymUOoZfUEDWn/sXBat4sSaBEtUDRDG1NOUml/fk1kDlDouyQ4vK+wM+ GQo6Yd32NDnxv5CHBR3bleFq/iMvQFDUvlQBfqh7OpvVOTq5ROPE2c6kuylI3vSJWMxBT8Ft5r BSa1IpD3NQUlxJVyJzcHvEPiNuVVS2zvqEdh9dIJyXZPVH3PD2kJgoLVK2Y6/M9kbkQ5Gm9m2y ksI= Received: from orw-gwy-02-in.mentorg.com ([192.94.38.167]) by esa2.mentor.iphmx.com with ESMTP; 16 Dec 2019 15:18:28 -0800 IronPort-SDR: rs3F/nRuvxIdrqqxwD02dYyZnmZO7/xjkCmeIz2vIsG/26e11otuo3zBMWClMVZd6dTWImZqrr 4lz7bvnuUNQujv2F1bfoxYfISgOl7M6iX0l1lBKPxrZzanuYPctagDV44aYhql3eUfvgANRwhQ ++1/ohxOzeVckuYYOeTyUPugiBkHCp3VZAlqLxhOygE1HtZm4z3PQZY+YKt7omtBfL/blp8wqQ UVGmGFkRfpikCBEMOANpgn2/giVpQswaGre11h3A17O4j+m0AAUi0cWPSuaJLhUfisFkxnPjW4 nGs= Date: Mon, 16 Dec 2019 23:18:00 -0000 From: Joseph Myers To: Segher Boessenkool CC: Jeff Law , Mark Wielaard , Maxim Kuvyrkov , "Richard Earnshaw (lists)" , , Subject: Re: Proposal for the transition timetable for the move to GIT In-Reply-To: <20191216215927.GG3152@gate.crashing.org> Message-ID: References: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> <9E009921-96EA-44A2-A06A-232711227E69@linaro.org> <0fb81074d87c96b3312565800b8bfc25cfcbe179.camel@redhat.com> <20191216215927.GG3152@gate.crashing.org> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-Path: joseph@codesourcery.com X-SW-Source: 2019-12/txt/msg00255.txt.bz2 On Mon, 16 Dec 2019, Segher Boessenkool wrote: > Hi, > > On Mon, Dec 16, 2019 at 05:07:48PM +0000, Joseph Myers wrote: > > Yes. It should be possible to confirm branch tip conversions and other > > properties of the repository (e.g. that all branch tips are properly > > descended from the first commit on trunk except for the specific branches > > that shouldn't be) once my current conversions have finished running. > > Please do that for Maxim's conversion as well then? > > (If the way you do the verification requires reposurgeon, the > verification methodology itself is fatally flawed). It does not require reposurgeon. The inputs for verification of branch tips are (a) a list of correspondences between SVN paths and git refs and (b) the SVN revision number at which those refs should correspond to those SVN paths. A list can readily be generated for any git repository not using too complicated a mapping from SVN branch names (with a more complicated mapping, it's natural for the process modifying the names also to generate the list for use in verification). > > * Richard's improvements to commit messages are a great improvement to the > > resulting repository (and it's OK if a small percentage end up misleading > > because someone used the wrong PR number, sometimes people use the wrong > > commit message or commit changes they didn't mean to and so having some > > misleading messages is unavoidable). > > As long as the original commit message is kept, verbatim, and you only > add a new summary line, all is fine. If not -> nope, not okay. That is how it works. A new summary line is added, with the original message kept verbatim after that. -- Joseph S. Myers joseph@codesourcery.com