From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 126017 invoked by alias); 16 Dec 2019 09:53:10 -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 126009 invoked by uid 89); 16 Dec 2019 09:53:10 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.6 required=5.0 tests=AWL,BAYES_20,KAM_SHORT,SPF_PASS,T_FILL_THIS_FORM_SHORT autolearn=ham version=3.3.1 spammy=january, January, sk:Richard, Kuvyrkov X-HELO: gnu.wildebeest.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (212.238.236.112) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 16 Dec 2019 09:53:08 +0000 Received: from tarox.wildebeest.org (tarox.wildebeest.org [172.31.17.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 734C130278BD; Mon, 16 Dec 2019 10:53:05 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 2EE52400B8DB; Mon, 16 Dec 2019 10:53:05 +0100 (CET) Message-ID: Subject: Re: Proposal for the transition timetable for the move to GIT From: Mark Wielaard To: Maxim Kuvyrkov Cc: "Richard Earnshaw (lists)" , gcc@gcc.gnu.org Date: Mon, 16 Dec 2019 09:53:00 -0000 In-Reply-To: References: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> <9E009921-96EA-44A2-A06A-232711227E69@linaro.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 X-SW-Source: 2019-12/txt/msg00220.txt.bz2 Hi Maxim, On Fri, 2019-12-06 at 17:44 +0300, Maxim Kuvyrkov wrote: > > On Sep 19, 2019, at 6:34 PM, Maxim Kuvyrkov = wrote: > > > On Sep 17, 2019, at 3:02 PM, Richard Earnshaw (lists) wrote: > > >=20 > > > Monday 16th December 2019 - cut off date for picking which git conver= sion to use > > >=20 > > > Tuesday 31st December 2019 - SVN repo becomes read-only at end of sta= ge 3. > > >=20 > > > Thursday 2nd January 2020 - (ie read-only + 2 days) new git repo come= s on line for live commits. > >=20 > > I have regenerated my primary version this week, and it's up at > > https://git.linaro.org/people/maxim-kuvyrkov/gcc-pretty.git/ . > > So far I have received only minor issue reports about it, and all known= problems have been fixed. > > I could use a bit more scrutiny :-). >=20 > I think now is a good time to give status update on the svn->git conversi= on I maintain. > See https://git.linaro.org/people/maxim-kuvyrkov/gcc-pretty.git/ . >=20 > 1. The conversion has all SVN live branches converted as branches under r= efs/heads/* . >=20 > 2. The conversion has all SVN live tags converted as annotated tags under= refs/tags/* . >=20 > 3. If desired, it would be trivial to add all deleted / leaf SVN branches= and tags. > They would be named as branches/my-deleted-branch@12345, > where @12345 is the revision at which the branch was deleted. > Branches created and deleted multiple times would have separate entries > corresponding to delete revisions. >=20 > 4. Git committer and git author entries are very accurate > (imo, better than reposurgeon's, but I'm biased). > Developers' names and email addresses are mined from commit logs, > changelogs and source code and have historically-accurately attributio= ns > to employer's email addresses. >=20 > 5. Since there is interest in reparenting branches to fix cvs2svn merge i= ssues, > I've added this feature to my scripts as well (turned out to be trivia= l). > I'll keep the original gcc-pretty.git repo intact and will upload the = new one at > https://git.linaro.org/people/maxim-kuvyrkov/gcc-reparent.git/ > -- should be live by Monday. Should we go with the gcc-reparent.git repo now? Where exactly should it be installed under https://gcc.gnu.org/git/ Replacing the existing gcc.git will be confusing, but then how would we name the repo that will become the main git gcc repo in 2 weeks? Where are the tools/scripts that should be installed on gcc.gnu.org to keep it up to date during the next 2 week transition period? Thanks, Mark