From: "Joseph S. Myers" <joseph@codesourcery.com>
To: gcc-patches@gcc.gnu.org
Cc: rth@redhat.com, jh@suse.cz, ubizjak@gmail.com,
thomas@schwinge.name, rmh@gnu.org
Subject: Ping Re: Split up config/i386/linux.h etc.
Date: Mon, 11 Apr 2011 12:55:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1104111253540.26644@digraph.polyomino.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1104042352090.552@digraph.polyomino.org.uk>
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.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-04-11 12:55 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 ` Joseph S. Myers [this message]
2011-04-11 17:07 ` Ping " Richard Henderson
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=Pine.LNX.4.64.1104111253540.26644@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=rmh@gnu.org \
--cc=rth@redhat.com \
--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).