public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sourceware.org, Openrisc <openrisc@lists.librecores.org>
Subject: Re: [PATCH 0/2] CGEN unordered fpu compares + fixes
Date: Wed, 12 Jun 2019 20:53:00 -0000	[thread overview]
Message-ID: <20190612205331.GG2358@lianli.shorne-pla.net> (raw)
In-Reply-To: <20190612150440.GA31262@redhat.com>

On Wed, Jun 12, 2019 at 11:04:40AM -0400, Frank Ch. Eigler wrote:
> Hi -
> 
> > Did anyone have a chance to look at this?  The binutils patches that require
> > this are approved, but I rather not commit them unless this I get OK on these
> > patches and push them.
> 
> These are merged, thanks.

Thanks,

Note, I noticed the changelog was not updated.  I usually do that as part of the
final phase up pushing the changes to git.

Or did we stop maintaining the change log when moving to git (I would have no
problem with that myself ;) )?

-Stafford

  reply	other threads:[~2019-06-12 20:53 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 [this message]
2019-06-12 21:54       ` Frank Ch. Eigler
2019-06-13  8:51         ` Jose E. Marchesi
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=20190612205331.GG2358@lianli.shorne-pla.net \
    --to=shorne@gmail.com \
    --cc=cgen@sourceware.org \
    --cc=fche@redhat.com \
    --cc=openrisc@lists.librecores.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).