public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/3082
Date: Fri, 08 Jun 2001 06:26:00 -0000 [thread overview]
Message-ID: <20010608132601.27360.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c++/3082; it has been noted by GNATS.
From: Nathan Sidwell <nathan@codesourcery.com>
To: ljrittle@acm.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/3082
Date: Fri, 08 Jun 2001 14:24:22 +0100
Loren,
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3082&database=gcc
I agreee, this should be high priority.
> Patch posted to libstdc++-v3, gcc-patches and installed on mainline
are you refering to http://gcc.gnu.org/ml/gcc-patches/2001-06/msg00325.html
or something else? Have you booted that patch on a 3.0 prerelease?
Please provide cluons :-)
nathan
--
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next reply other threads:[~2001-06-08 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-08 6:26 Nathan Sidwell [this message]
2001-06-08 12:06 c++/3082 Loren James Rittle
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=20010608132601.27360.qmail@sourceware.cygnus.com \
--to=nathan@codesourcery.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).