public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "owner at bugs dot debian.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/10350] thread-safety problem in std::string.
Date: Mon, 17 Feb 2014 18:18:00 -0000 [thread overview]
Message-ID: <bug-10350-4-WJgN8gV37O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-10350-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10350
--- Comment #12 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Debian GCC Maintainers <debian-gcc@lists.debian.org>
If you wish to submit further information on this problem, please
send it to 140201@bugs.debian.org.
Please do not send mail to owner@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.
next prev parent reply other threads:[~2014-02-17 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10350-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 13:17 ` jackie.rosen at hushmail dot com
2014-02-16 13:39 ` owner at bugs dot debian.org
2014-02-17 18:18 ` owner at bugs dot debian.org [this message]
[not found] <20030408161601.10350.jkanze@caicheuvreuse.com>
2003-06-08 8:27 ` dhazeghi@yahoo.com
2003-06-09 16:29 ` bkoz@redhat.com
2003-06-11 15:43 ` dhazeghi@yahoo.com
2003-06-28 19:15 ` pinskia at physics dot uc dot edu
2003-08-10 3:22 ` pinskia at gcc dot gnu dot org
2003-08-10 3:23 ` pinskia at gcc dot gnu dot org
2005-05-02 13:32 ` pcarlini at suse dot de
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-10350-4-WJgN8gV37O@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).