From: Paolo Carlini <paolo.carlini@oracle.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>
Subject: [Ping] Re: [C++ Patch] PR 63985
Date: Mon, 22 Dec 2014 16:38:00 -0000 [thread overview]
Message-ID: <549848BF.8050302@oracle.com> (raw)
In-Reply-To: <54805981.6050501@oracle.com>
Hi,
On 12/04/2014 01:54 PM, Paolo Carlini wrote:
> ... oops, sent the wrong patch. See the below instead.
>
> Paolo.
It occurs to me that a while ago I sent this patch: what do you think?
Is the diagnostic good enough?
https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00376.html
https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00378.html
Thanks,
Paolo.
next prev parent reply other threads:[~2014-12-22 16:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 12:51 Paolo Carlini
2014-12-04 12:54 ` Paolo Carlini
2014-12-22 16:38 ` Paolo Carlini [this message]
2014-12-22 18:57 ` Jason Merrill
2014-12-22 20:26 ` Paolo Carlini
2014-12-22 21:14 ` Jason Merrill
2014-12-22 21:58 ` Paolo Carlini
2014-12-22 22:56 ` Jason Merrill
2014-12-23 16:31 ` Paolo Carlini
2014-12-23 16:46 ` Paolo Carlini
2014-12-23 18:39 ` Jason Merrill
2014-12-23 21:02 ` Paolo Carlini
2014-12-23 22:24 ` Jason Merrill
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=549848BF.8050302@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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).