From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 68028 invoked by alias); 11 Dec 2019 16:02:39 -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 68014 invoked by uid 89); 11 Dec 2019 16:02:38 -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=HX-Received:a5d, hear X-HELO: mail-wr1-f68.google.com Received: from mail-wr1-f68.google.com (HELO mail-wr1-f68.google.com) (209.85.221.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 11 Dec 2019 16:02:33 +0000 Received: by mail-wr1-f68.google.com with SMTP id q10so24609066wrm.11 for ; Wed, 11 Dec 2019 08:02:33 -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=Irx4cnvRhuZRk8UZjxFKo/PieccqS9MFBujkNF2Ct5w=; b=GOZbRbpvnfxXScN0COwIlNzm+508xtXWIbj8R/1Zv8BQ6p0eTMAqa/q0LEaFQZDnm8 h4CWxVouc/dJvT2VzSm36rQbMNsCH8elfGQylynaxuOXAeEGlLCaR1eQMdkDx+fp5IR1 PaR89+zr8rPLayN/AUJbNV0ij6LMvyl1xC+IrhgP9rveAWbexcBQkeBbn7r+CYg6vO5x JA0CgkHdZ3FeA/UBoHHR4BrAa2h/sAKHZ9J1x7bdHvYFkyYCvQj3iuG0+2VSrujSdyY9 C66Hoiel5aKLrRmPT2j8WUk/x9j3TtaVVsVeuIavICUQ4nx1k2gieFvTCMmJMWWv/gYh D6oQ== MIME-Version: 1.0 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> In-Reply-To: From: Jonathan Wakely Date: Wed, 11 Dec 2019 16:02:00 -0000 Message-ID: Subject: Re: Proposal for the transition timetable for the move to GIT To: Joseph Myers Cc: "Richard Earnshaw (lists)" , Maxim Kuvyrkov , "Eric S. Raymond" , Richard Guenther , "gcc@gcc.gnu.org" Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00174.txt.bz2 On Wed, 11 Dec 2019 at 15:36, Joseph Myers wrote: > > On Wed, 11 Dec 2019, Richard Earnshaw (lists) wrote: > > > 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. > > Concretely: when I did a comparison of the tip of trunk against master > from a reposurgeon conversion on 29 November, there were 1421 differences > (files or directories only present in one of SVN or git or with different > contents). As of today with the SVN dump reader rewrite, this is down to > just two differences (plus two empty directories present in SVN as git > doesn't represent empty directories), and we understand exactly where the > problem arises with a trunk deletion and recreation and what's odd about > that particular trunk deletion and recreation. All the deleted tags and > branches are now placed neatly in refs/deleted/; we no longer have any > problems with deleted tags or branches wrongly appearing in the main tag > and branch namespaces; all the mess with deleted branches appearing in the > reposurgeon-generated "root" branch has gone, everything there now appears > to relate to commits that genuinely and correctly do not go in any branch > or tag (changes to the hooks directory, branches wrongly created at top > level, etc.). Almost all the branches that previously weren't created in > git by reposurgeon because they were not changed in SVN after branch > creation are now properly present in the conversion to git. That's good news and I'm relieved to hear it. Thanks.