From: Andy Gibbs <andyg1001@hotmail.co.uk>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] __builtin_choose_expr *bump*
Date: Fri, 21 Oct 2011 15:39:00 -0000 [thread overview]
Message-ID: <BLU0-SMTP407FDBB5407A7C361C17D24E7E80@phx.gbl> (raw)
In-Reply-To: <Pine.LNX.4.64.1110211441200.23945@digraph.polyomino.org.uk>
On Friday, October 21, 2011 4:42 PM, Joseph S. Myers wrote:
> On Fri, 21 Oct 2011, Andy Gibbs wrote:
>
>> Hi,
>>
>> Please can I "bump" this patch and ask for it to be approved and
>> committed:
>> http://gcc.gnu.org/ml/gcc-patches/2011-10/msg01711.html
>
> Have you sent in your copyright assignment papers to the FSF? The patch
> is large enough to need them.
>
Yes, I have.
Regards,
Andy
prev parent reply other threads:[~2011-10-21 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 12:26 [C++ Patch] __builtin_choose_expr Andy Gibbs
2011-10-21 10:40 ` [C++ Patch] __builtin_choose_expr *bump* Andy Gibbs
2011-10-21 10:47 ` Richard Guenther
2011-10-21 14:29 ` Andy Gibbs
2011-10-21 15:28 ` Joseph S. Myers
2011-10-21 15:39 ` Andy Gibbs [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=BLU0-SMTP407FDBB5407A7C361C17D24E7E80@phx.gbl \
--to=andyg1001@hotmail.co.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).