From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32915 invoked by alias); 16 Dec 2019 12:43:54 -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 32903 invoked by uid 89); 16 Dec 2019 12:43:53 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.6 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,SPF_PASS autolearn=ham version=3.3.1 spammy= 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 12:43:51 +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 F366E30278BD; Mon, 16 Dec 2019 13:43:48 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 92EF640BA6A9; Mon, 16 Dec 2019 13:43:48 +0100 (CET) Message-ID: Subject: Re: Proposal for the transition timetable for the move to GIT From: Mark Wielaard To: Joseph Myers Cc: Maxim Kuvyrkov , "Richard Earnshaw (lists)" , gcc@gcc.gnu.org Date: Mon, 16 Dec 2019 12:43: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/msg00224.txt.bz2 On Mon, 2019-12-16 at 11:29 +0000, Joseph Myers wrote: > On Mon, 16 Dec 2019, Mark Wielaard wrote: >=20 > > Should we go with the gcc-reparent.git repo now? >=20 > I think we should go with the reposurgeon conversion, with all Richard's= =20 > improvements to commit messages. gcc-reparent.git has issues of its own;= =20 > at least, checking the list of branches shows some branches are missing.= =20=20 > So both conversions can still be considered works in progress. I thought we would pick the best available conversion today. If we keep tweaking the conversions till they are "perfect" we probably never reach that point. > However, we should also note that stage 3 is intended to last two months,= =20 > ending with the move to git=20 > =20 > , and given that it=20 > didn't start at the start of November as anticipated in the originally=20 > proposed timetable, that implies corresponding updates to all the dates.= =20=20 > By now, enough people are away until the new year that now isn't a good=20 > time for deciding things anyway. The idea was to do it while most people were away to have the least impact. The timeline https://gcc.gnu.org/wiki/GitConversion does say we can slip for logistical reasons the read-only date (2019/12/31) by a few days. Do people really want to keep tweaking the conversions and postpone the git switchover? What would the new timetable be then? Cheers, Mark