public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "3dw4rd at verizon dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60249] [c++11] Compiler goes into semi-infinite loop with wrong usage of user defined string literals
Date: Sat, 28 Jun 2014 14:48:00 -0000	[thread overview]
Message-ID: <bug-60249-4-62Zv6ZDNy9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60249-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249

--- Comment #10 from Ed Smith-Rowland <3dw4rd at verizon dot net> ---
On 06/28/2014 10:03 AM, paolo.carlini at oracle dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60249
>
> --- Comment #8 from Paolo Carlini <paolo.carlini at oracle dot com> ---
> Thanks, but in general I would recommend sending patches to gcc-patches in a
> separate email, with a clear [C++ Patch] or something similar in the subject.
> Also, please minimize jokes and other redundant content, we already have
> setious issues with lost patches, old bugs remaining umfixed for ages, etc,
> without.
>

Sorry about the noise.
Should I send a new cleaner message with new subject?


  parent reply	other threads:[~2014-06-28 14:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 21:18 [Bug c++/60249] New: " reichelt at gcc dot gnu.org
2014-04-17 13:38 ` [Bug c++/60249] " paolo.carlini at oracle dot com
2014-06-25 17:45 ` paolo.carlini at oracle dot com
2014-06-26 14:51 ` 3dw4rd at verizon dot net
2014-06-27 21:36 ` 3dw4rd at verizon dot net
2014-06-27 21:39 ` paolo.carlini at oracle dot com
2014-06-28 13:28 ` 3dw4rd at verizon dot net
2014-06-28 13:28 ` 3dw4rd at verizon dot net
2014-06-28 14:03 ` paolo.carlini at oracle dot com
2014-06-28 14:21 ` 3dw4rd at verizon dot net
2014-06-28 14:48 ` 3dw4rd at verizon dot net [this message]
2014-07-01  3:14 ` emsr at gcc dot gnu.org
2014-07-01  5:31 ` emsr at gcc dot gnu.org
2014-07-01  5:32 ` emsr at gcc dot gnu.org

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=bug-60249-4-62Zv6ZDNy9@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).