From: jemarch@gnu.org (Jose E. Marchesi)
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Stafford Horne <shorne@gmail.com>, cgen@sourceware.org
Subject: Re: [PATCH 0/2] CGEN unordered fpu compares + fixes
Date: Thu, 13 Jun 2019 08:51:00 -0000 [thread overview]
Message-ID: <87a7el7tr9.fsf@gnu.org> (raw)
In-Reply-To: <20190612215446.GA32764@redhat.com> (Frank Ch. Eigler's message of "Wed, 12 Jun 2019 17:54:46 -0400")
> 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.
next prev parent reply other threads:[~2019-06-13 8:51 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 1/2] cgen: Add unordered compare operation Stafford Horne
2019-06-01 7:26 ` [PATCH 2/2] gen-doc: Updates for latest cpu definitions 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 [this message]
2019-06-13 12:23 ` Stafford Horne
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=87a7el7tr9.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=cgen@sourceware.org \
--cc=fche@redhat.com \
--cc=shorne@gmail.com \
/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).