public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "shalja.rudra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53173] GCC 4.6.3 errors
Date: Fri, 04 May 2012 20:12:00 -0000 [thread overview]
Message-ID: <bug-53173-4-Nxbo4xuKwV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53173-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53173
--- Comment #10 from gcc <shalja.rudra at gmail dot com> 2012-05-04 20:11:50 UTC ---
I looked into the similar post in boost mailing list
http://lists.boost.org/Archives/boost/2011/07/184266.php and it directed to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49445
The email got bounced before using the gcc-help@gcc.gnu.org, may be the email
was not plain text format . It is fine now.
Thanks
(In reply to comment #9)
> Bugzilla is not a help forum. Please find somewhere more appropriate to ask
> how to solve your problems, such as the boost mailing list or the gcc-help
> list.
prev parent reply other threads:[~2012-05-04 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 19:02 [Bug c++/53173] New: PROD02 shalja.rudra at gmail dot com
2012-04-30 20:03 ` [Bug c++/53173] PROD02 marc.glisse at normalesup dot org
2012-04-30 20:32 ` shalja.rudra at gmail dot com
2012-05-01 9:37 ` redi at gcc dot gnu.org
2012-05-01 9:41 ` redi at gcc dot gnu.org
2012-05-01 9:41 ` redi at gcc dot gnu.org
2012-05-02 14:53 ` [Bug c++/53173] GCC 4.6.2 errors shalja.rudra at gmail dot com
2012-05-04 19:36 ` [Bug c++/53173] GCC 4.6.3 errors shalja.rudra at gmail dot com
2012-05-04 19:38 ` shalja.rudra at gmail dot com
2012-05-04 19:47 ` redi at gcc dot gnu.org
2012-05-04 20:12 ` shalja.rudra at gmail dot com [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=bug-53173-4-Nxbo4xuKwV@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).