From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 39153 invoked by alias); 19 Dec 2019 00:57:40 -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 39145 invoked by uid 89); 19 Dec 2019 00:57:40 -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=Nor 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; Thu, 19 Dec 2019 00:57:38 +0000 Received: by snark.thyrsus.com (Postfix, from userid 1000) id 29A3647049F5; Wed, 18 Dec 2019 19:57:36 -0500 (EST) Date: Thu, 19 Dec 2019 00:57:00 -0000 From: "Eric S. Raymond" To: Joseph Myers Cc: Jeff Law , Segher Boessenkool , 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: <20191219005736.GB18966@thyrsus.com> Reply-To: esr@thyrsus.com References: <0fb81074d87c96b3312565800b8bfc25cfcbe179.camel@redhat.com> <20191216215927.GG3152@gate.crashing.org> <20191216224244.GI3152@gate.crashing.org> <5ea5dd673eb006dd84af7e47fcbab53a15e8005d.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/msg00293.txt.bz2 Joseph Myers : > Nor do I think reposurgeon (or at least the SVN reader, which is the main > part engaged here) is significantly more complicated than implied by the > task it's performing of translating between the different conceptual > models of SVN and git. I've found it straightforward to produce reduced > testcases for issues found, and fixed several of them myself despite not > actually knowing Go. The issues remaining are generally conceptually > straightforward to understand the issue and how to fix it. Let me note for the record that I found Joseph's ability to find and fix bugs in the reader quite impressive. Maybe not as impressive as it would have been before the recent rewrite. That code used to be a pretty nasty hairball. It's a lot cleaner and easier to understand now. But impedence-matching the two data models is tricky, subtler than it looks, and has rebarbative edge cases. Even given the ckeanest possible implementatiion, troubleshooting it is no mean feat. -- Eric S. Raymond