public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: "Jose E. Marchesi" <jemarch@gnu.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, cgen@sourceware.org
Subject: Re: [PATCH 0/2] CGEN unordered fpu compares + fixes
Date: Thu, 13 Jun 2019 12:23:00 -0000	[thread overview]
Message-ID: <20190613122318.GI2358@lianli.shorne-pla.net> (raw)
In-Reply-To: <87a7el7tr9.fsf@gnu.org>

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

  reply	other threads:[~2019-06-13 12:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-01  7:26 Stafford Horne
2019-06-01  7:26 ` [PATCH 2/2] gen-doc: Updates for latest cpu definitions Stafford Horne
2019-06-01  7:26 ` [PATCH 1/2] cgen: Add unordered compare operation Stafford Horne
2019-06-12 13:14 ` [PATCH 0/2] CGEN unordered fpu compares + fixes Stafford Horne
2019-06-12 14:36   ` Jose E. Marchesi
2019-06-12 15:04   ` Frank Ch. Eigler
2019-06-12 20:53     ` Stafford Horne
2019-06-12 21:54       ` Frank Ch. Eigler
2019-06-13  8:51         ` Jose E. Marchesi
2019-06-13 12:23           ` Stafford Horne [this message]
2019-06-13 15:02             ` Jose E. Marchesi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190613122318.GI2358@lianli.shorne-pla.net \
    --to=shorne@gmail.com \
    --cc=cgen@sourceware.org \
    --cc=fche@redhat.com \
    --cc=jemarch@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).