From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27585 invoked by alias); 16 Dec 2019 13:54:56 -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 27462 invoked by uid 89); 16 Dec 2019 13:54:55 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=raymond, crew, HX-Languages-Length:828, esr X-HELO: snark.thyrsus.com Received: from thyrsus.com (HELO snark.thyrsus.com) (71.162.243.5) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 16 Dec 2019 13:54:53 +0000 Received: by snark.thyrsus.com (Postfix, from userid 1000) id F32E74704C1B; Mon, 16 Dec 2019 08:54:51 -0500 (EST) Date: Mon, 16 Dec 2019 13:54:00 -0000 From: "Eric S. Raymond" To: Segher Boessenkool Cc: Mark Wielaard , Joseph Myers , Maxim Kuvyrkov , "Richard Earnshaw (lists)" , gcc@gcc.gnu.org Subject: Re: Proposal for the transition timetable for the move to GIT Message-ID: <20191216135451.GA3142@thyrsus.com> Reply-To: esr@thyrsus.com References: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> <9E009921-96EA-44A2-A06A-232711227E69@linaro.org> <20191216133632.GC3152@gate.crashing.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191216133632.GC3152@gate.crashing.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00230.txt.bz2 Segher Boessenkool : > > Do people really want to keep tweaking the conversions and postpone the > > git switchover? > > No. It may not be my place to say, but...I think the stakes are pretty high here. If I were a GCC developer, I think I'd want the best possible conversion even if that takes a little longer. jsm28, rearnsha, and my reposurgeon crew are pretty close to a final deliverable now. We know what the remaining issues are, they're not major, and we have a strategy for fixing them. Have a little patience, please. Better yet, come over to #reposurgeon on freenode and help out. Anyone who can run tests on a machine with >128GB RAM would be especially welcome. -- Eric S. Raymond