public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Terry Guo <terry.guo@arm.com>
Cc: libstdc <libstdc++@gcc.gnu.org>,
	gcc-patches Patches <gcc-patches@gcc.gnu.org>,
	Jonathan Wakely <jwakely.gcc@gmail.com>,
	Rainer Orth <ro@cebitec.uni-bielefeld.de>,
	Richard Earnshaw <Richard.Earnshaw@arm.com>,
	Paolo Bonzini <bonzini@gnu.org>
Subject: Re: [Ping][PATCH, libstdc++-v3] Enable to cross-test libstdc++ on simulator
Date: Mon, 12 Mar 2012 18:52:00 -0000	[thread overview]
Message-ID: <1E44F927-C15B-4D2F-BC91-1EF08B32557D@comcast.net> (raw)
In-Reply-To: <CAH6eHdTj7sML1E4YOkqXT4mMNXHn3t4W6Pc3Whf+MHXcqStZhw@mail.gmail.com>

On Mar 10, 2012, at 3:25 PM, Jonathan Wakely wrote:
> On 7 March 2012 05:22, Terry Guo wrote:
>> Hello,
>> 
>> Can anybody please review and approve the following simple patch? Thanks
>> very much.
>> 
>> http://gcc.gnu.org/ml/libstdc++/2011-08/msg00063.html

Ok.  Ok for the release branches as relevant, if they are open for changes, after testing.  If you backport it, let it brew for at least a week on trunk before any backports.  Thanks.

  parent reply	other threads:[~2012-03-12 18:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4f56f0ab.c107440a.725e.3322SMTPIN_ADDED@mx.google.com>
2012-03-07  8:56 ` Jonathan Wakely
2012-03-10 23:25 ` Jonathan Wakely
2012-03-12  2:18   ` Terry Guo
2012-03-12 18:52   ` Mike Stump [this message]
2012-03-28  1:15 Terry Guo
2012-03-28  1:18 ` Paolo Carlini
2012-04-06  7:49   ` Terry Guo
2012-04-06 13:27     ` Mike Stump
  -- strict thread matches above, loose matches on Subject: below --
2012-03-07  5:22 Terry Guo
2012-03-23 12:44 ` Paolo Carlini
2012-03-23 13:03   ` Paolo Bonzini
2012-03-23 13:38     ` Paolo Carlini

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=1E44F927-C15B-4D2F-BC91-1EF08B32557D@comcast.net \
    --to=mikestump@comcast.net \
    --cc=Richard.Earnshaw@arm.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ro@cebitec.uni-bielefeld.de \
    --cc=terry.guo@arm.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).