From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 106866 invoked by alias); 16 Dec 2019 19:15:24 -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 106759 invoked by uid 89); 16 Dec 2019 19:15:15 -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=our 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 19:15:14 +0000 Received: by snark.thyrsus.com (Postfix, from userid 1000) id 8F48D4704E3D; Mon, 16 Dec 2019 14:15:11 -0500 (EST) Date: Mon, 16 Dec 2019 19:15:00 -0000 From: "Eric S. Raymond" To: Joseph Myers Cc: Jeff Law , Mark Wielaard , Maxim Kuvyrkov , "Richard Earnshaw (lists)" , gcc@gcc.gnu.org Subject: Re: Proposal for the transition timetable for the move to GIT Message-ID: <20191216191511.GA70647@thyrsus.com> Reply-To: esr@thyrsus.com References: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> <9E009921-96EA-44A2-A06A-232711227E69@linaro.org> <0fb81074d87c96b3312565800b8bfc25cfcbe179.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00250.txt.bz2 Joseph Myers : > * As we're part of the free software community as a whole rather than > something in isolation, choosing to make a general-purpose tool work for > our conversion is somewhat preferable to choosing an ad hoc approach > because it contributes something of value for other repository conversions > by other projects in future. That's not just theory or sentiment. Reposurgeon is the best any-VCS-to-any-VCS converter there is because every time I do a conversion, I learn things, and that knowledge gets incorporated in the code and the documentation around it. Yes, in theory someone else could build a tool as good that incorporates as much domain knowledge. So far, nobody has tried. It's unlikely anyone will, at this point, when they can join my dev team and get the results they want with much less effort by improving reposurgeon or one of its auxiliary tools. Every time that happens, everybody - into the indefinite future - wins. -- Eric S. Raymond