From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8361 invoked by alias); 13 Jun 2019 12:23:24 -0000 Mailing-List: contact cgen-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sourceware.org Received: (qmail 8353 invoked by uid 89); 13 Jun 2019 12:23:24 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-10.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=Jose, jose, sk:changel, HTo:U*jemarch X-HELO: mail-pf1-f194.google.com Received: from mail-pf1-f194.google.com (HELO mail-pf1-f194.google.com) (209.85.210.194) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 13 Jun 2019 12:23:22 +0000 Received: by mail-pf1-f194.google.com with SMTP id x15so11784580pfq.0 for ; Thu, 13 Jun 2019 05:23:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=IwSUHpSECdb8u3vClqenphw/MqeA6XM36TYmOHlI37g=; b=RmlFickBp35ecjIO7Q+SB7aXkPM4xap1ehBLYB71oab4/ZY66UGa5XRRafTBzTxWaw 0zBlUxySog8N18ZwwHTjYc8z9cb6AFsnQW7q5jY9QluTQIEHYBeehWWyY625Yt4yKy4M xsxxVepT0UQ9h/Qs4T/ekQgYUsbBivAgxtU86d92j6zYKMNOkm6bqUwc46ydVCPd7XxY A9dFXnV0FDMbPwbCd0M/uB0I4uBExM4rpp1oPO4/Sc8WUUDFOyLYjrvQZsjYgUSZzfGS IXYGx2X6L95A4N3N1JNxIVBMD8s6K642M1jTSSCScfHeYSl82yJeWm7Fmd/Ui8ZEKL7l SrEQ== Return-Path: Received: from localhost (g30.211-19-85.ppp.wakwak.ne.jp. [211.19.85.30]) by smtp.gmail.com with ESMTPSA id d13sm1914673pjs.32.2019.06.13.05.23.20 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Thu, 13 Jun 2019 05:23:20 -0700 (PDT) Date: Thu, 13 Jun 2019 12:23:00 -0000 From: Stafford Horne To: "Jose E. Marchesi" Cc: "Frank Ch. Eigler" , cgen@sourceware.org Subject: Re: [PATCH 0/2] CGEN unordered fpu compares + fixes Message-ID: <20190613122318.GI2358@lianli.shorne-pla.net> References: <20190601072629.4070-1-shorne@gmail.com> <20190612131403.GE2358@lianli.shorne-pla.net> <20190612150440.GA31262@redhat.com> <20190612205331.GG2358@lianli.shorne-pla.net> <20190612215446.GA32764@redhat.com> <87a7el7tr9.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87a7el7tr9.fsf@gnu.org> User-Agent: Mutt/1.11.4 (2019-03-13) X-IsSubscribed: yes X-SW-Source: 2019-q2/txt/msg00025.txt.bz2 On Thu, Jun 13, 2019 at 10:51:38AM +0200, Jose E. Marchesi wrote: > > > Or did we stop maintaining the change log when moving to git (I would have no > > problem with that myself ;) )? > > I'm not sure who is in a position to make an executive decision in the > matter. I'm for it myself. Is there someone who wishes to speak up > in defense of ChangeLog files? > > I have been suffering ChangeLogs myself for a long time, and it would be > great to stop maintaining them by hand. IMO we should do whatever is > done in binutils, to not jeopardize a possible future integration. > Ditto for becoming official GNU software. For binutils we maintain the ChangeLog. I suggest keeping it until there is a consensus on all GNU projects. It does help with grepping things sometimes. Note, a tool I use to maintain the ChangeLog is: - https://github.com/simark/gnu-changelog-tools The idea with this tool is that you maintain your changelog entry in your git commit messages until you are about to commit. When you want to push your changes up to git just run a rebase...: $ EDITOR=/bin/true git rebase master -i --exec changelog-git-amend.py And it will put the right date and copy the changelog from the git commit message to the ChangeLog file at needed. -Stafford