From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 46926 invoked by alias); 25 Dec 2019 12:23:23 -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 46918 invoked by uid 89); 25 Dec 2019 12:23:22 -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=fragile, five, growing, sk:changel 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; Wed, 25 Dec 2019 12:23:21 +0000 Received: by snark.thyrsus.com (Postfix, from userid 1000) id 589CC4704BBA; Wed, 25 Dec 2019 07:23:20 -0500 (EST) Date: Wed, 25 Dec 2019 12:23:00 -0000 From: "Eric S. Raymond" To: Joseph Myers Cc: Roman Zhuykov , Segher Boessenkool , gcc@gcc.gnu.org, Alexander Monakov , Maxim Kuvyrkov , Richard.Earnshaw@arm.com, rearnsha@gmail.com Subject: Re: Test GCC conversion with reposurgeon available Message-ID: <20191225122320.GB96669@thyrsus.com> Reply-To: esr@thyrsus.com References: <28ca5dbe-a29e-7f1e-a599-d80709643421@ispras.ru> <20191224155543.GH4505@gate.crashing.org> <20191224181444.GJ4505@gate.crashing.org> <279bf8dd-8725-c3fa-0def-130b3d128509@ispras.ru> 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/msg00404.txt.bz2 Joseph Myers : > These are all cases covered by the request-for-enhancement issue for > adding Co-Authored-by: when the ChangeLog header names multiple authors, > as the corresponding de facto git idiom for that case. I apologize, but I am growing doubtful I can deliver that. Even if I can, it may take longer than your conversion schedule allows given that we've only got five days on the clock. Here are the problems: 1. I don't have a reduced test case to validate parsing against. 2. The ChangeLog-parsing code is fragile and difficult to modify. This is inherent - the syntactic cues it's working with are weak and false matches are all too easy. I've got to have 1 before I can even try to deal with 2. -- Eric S. Raymond