public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, jh@suse.cz, ubizjak@gmail.com,
	       thomas@schwinge.name, rmh@gnu.org
Subject: Re: Ping Re: Split up config/i386/linux.h etc.
Date: Mon, 11 Apr 2011 17:07:00 -0000	[thread overview]
Message-ID: <4DA33542.5020502@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1104111253540.26644@digraph.polyomino.org.uk>

On 04/11/2011 05:55 AM, Joseph S. Myers wrote:
> Ping.  This patch 
> <http://gcc.gnu.org/ml/gcc-patches/2011-04/msg00276.html> is pending 
> review.  There's also a followup patch 
> <http://gcc.gnu.org/ml/gcc-patches/2011-04/msg00489.html> pending review.
> 

Both ok.


r~

      reply	other threads:[~2011-04-11 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 23:55 Joseph S. Myers
2011-04-11 12:55 ` Ping " Joseph S. Myers
2011-04-11 17:07   ` Richard Henderson [this message]

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=4DA33542.5020502@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jh@suse.cz \
    --cc=joseph@codesourcery.com \
    --cc=rmh@gnu.org \
    --cc=thomas@schwinge.name \
    --cc=ubizjak@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).