public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, snyder@fnal.gov Subject: Re: libstdc++/2977: string.h doesn't always inject names into std:: Date: Mon, 11 Jun 2001 16:21:00 -0000 [thread overview] Message-ID: <20010611232150.26605.qmail@sourceware.cygnus.com> (raw) Synopsis: string.h doesn't always inject names into std:: Responsible-Changed-From-To: unassigned->bkoz Responsible-Changed-By: bkoz Responsible-Changed-When: Mon Jun 11 16:21:50 2001 Responsible-Changed-Why: Mine. State-Changed-From-To: open->closed State-Changed-By: bkoz State-Changed-When: Mon Jun 11 16:21:50 2001 State-Changed-Why: Scott this stuff was fixed this weekend. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2977&database=gcc
next reply other threads:[~2001-06-11 16:21 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-11 16:21 bkoz [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-05-27 22:06 snyder
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=20010611232150.26605.qmail@sourceware.cygnus.com \ --to=bkoz@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=snyder@fnal.gov \ /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: linkBe 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).