From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 110871 invoked by alias); 16 Dec 2019 23:19:31 -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 110831 invoked by uid 89); 16 Dec 2019 23:19:30 -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=vulnerability, prototyping, earth, shipping 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 23:19:29 +0000 Received: by snark.thyrsus.com (Postfix, from userid 1000) id 770994704E4D; Mon, 16 Dec 2019 18:19:26 -0500 (EST) Date: Mon, 16 Dec 2019 23:19:00 -0000 From: "Eric S. Raymond" To: Segher Boessenkool Cc: Joseph Myers , 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: <20191216231926.GA56526@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> <20191216215927.GG3152@gate.crashing.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191216215927.GG3152@gate.crashing.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00256.txt.bz2 Segher Boessenkool : > There is absolutely no reason to trust a system that supposedly was > already very mature, but that required lots of complex modifications, > and even a complete rewrite in a different language, that even has its > own bug tracker, to work without problems (although we all have *seen* > some of its many problems over the last years), and at the same time > bad-mouthing simple scripts that simply work, and have simple problems. Some factual corrections: I didn't port to Go to fix bugs, I ported for better performance. Python is a wonderful language for prototyping a tool like this, but it's too slow and memory-hungry for use at the GCC conversion's scale. Also doesn't parallelize worth a damn. I very carefully *didn't* bad-mouth Maxim's scripts - in facrt I have said on-list that I think his approach is on the whole pretty intelligent. To anyone who didn't have some of the experiences I have had, even using git-svn to analyze basic blocks would appear reasonable and I don't actually fault Maxim for it. I *did* bad-mouth git-svn - and I will continue to do so until it no longer troubles the world with botched conversions. Relying on it is, in my subject-matter-expert opinion, unacceptably risky. While I don't blame Maxim for not being aware of this, it remains a serious vulnerability in his pipeline. I don't know how it is on your planet, but here on Earth having a bug tracker - and keeping it reasonably clean - is generally considered a sign of responsible maintainership. In conclusion, I'm happy that you're so concerned about bugs in reposurgeon. I am too. You're welcome to file issues and help us improve our already-extensive test suite by shipping us dumps that produce errors. -- Eric S. Raymond