public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: paolo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/5133: Problems with toupper
Date: Fri, 22 Nov 2002 05:43:00 -0000 [thread overview]
Message-ID: <20021116082604.10592.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/5133; it has been noted by GNATS.
From: Phil Edwards <phil@jaj.com>
To: Pete Ratzlaff <rpete@legs.harvard.edu>
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, paolo@gcc.gnu.org,
schmid@snake.iap.physik.tu-darmstadt.de
Subject: Re: libstdc++/5133: Problems with toupper
Date: Sat, 16 Nov 2002 03:21:45 -0500
On Sat, Nov 16, 2002 at 12:19:40AM -0500, Pete Ratzlaff wrote:
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5133
>
> Apologies, forgot to put the audit trail in my message.
No need to, it's appended by the mailing list software. Thanks for the
thought, though.
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
next reply other threads:[~2002-11-16 8:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 5:43 Phil Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-22 14:46 Pete Ratzlaff
2002-11-22 13:48 Martin Sebor
2002-11-22 5:41 Pete Ratzlaff
2002-11-22 5:11 Pete Ratzlaff
2002-10-31 16:08 paolo
2002-06-27 23:14 Christopher Currie
2001-12-17 8:06 Philip Martin
2001-12-16 17:46 Martin Sebor
2001-12-16 15:46 Peter Schmid
2001-12-16 13:53 paolo
2001-12-16 13:16 Peter Schmid
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=20021116082604.10592.qmail@sources.redhat.com \
--to=phil@jaj.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=paolo@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).