public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49132] [DR 178] Aggregate-initialization rejected for class with const data member
Date: Tue, 24 May 2011 00:42:00 -0000	[thread overview]
Message-ID: <bug-49132-4-vfeNsuxtg3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49132-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49132

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-05-23 23:16:02 UTC ---
(In reply to comment #2)
> It's annoying how GCC bugzilla tends not to send mail to people when I add them
> to CC even if I also add a comment.  Anyway, Fabien, please take a look at this
> bug.

GCC bugzilla mails seem to go out in random order with arbitrarily long delays
recently, so the "New" bug mail sometimes appears in the archives several
minutes after the first comment on a bug. very annoying


  parent reply	other threads:[~2011-05-23 23:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 21:46 [Bug c++/49132] New: [C++0x] " daniel.kruegler at googlemail dot com
2011-05-23 22:37 ` [Bug c++/49132] [DR 178] " jason at gcc dot gnu.org
2011-05-23 22:37 ` [Bug c++/49132] [C++0x] " jason at gcc dot gnu.org
2011-05-23 22:40 ` [Bug c++/49132] [4.6/4.7 regression] " jason at gcc dot gnu.org
2011-05-23 22:43 ` [Bug c++/49132] [C++0x] " jason at gcc dot gnu.org
2011-05-23 22:48 ` [Bug c++/49132] " jason at gcc dot gnu.org
2011-05-24  0:42 ` redi at gcc dot gnu.org [this message]
2011-11-16 13:55 ` [Bug c++/49132] [DR 178] " fabien at gcc dot gnu.org
2014-06-24 18:41 ` paolo.carlini at oracle dot com
2014-06-25 14:28 ` paolo at gcc dot gnu.org
2014-06-25 14:29 ` paolo.carlini at oracle dot com
2014-06-26 17:00 ` paolo.carlini at oracle dot com

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-49132-4-vfeNsuxtg3@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).