From: Benjamin Kosnik <bkoz@redhat.com>
To: mark@codesourcery.com
Cc: nickc@redhat.com, rearnsha@arm.com, jakub@redhat.com,
rth@redhat.com, gcc@gcc.gnu.org
Subject: Re: GCC 3.2.1 -- Request for Bug Fixers
Date: Fri, 25 Oct 2002 06:51:00 -0000 [thread overview]
Message-ID: <20021024154824.652060c1.bkoz@redhat.com> (raw)
In-Reply-To: <200210240005.g9O05Lf09720@gandalf.codesourcery.com>
>Benjamin -- PR 6476 is a libstdc++ issue assigned to you. I know you're
>figuring out madness what to put in the next version of the C++
>library this week, but find some time to nail this PR. :-)
I'm on the road for the next couple of days. I'll move this up to high
priority, so that as soon as I'm in one place, I'll try to nail it.
-benjamin
next prev parent reply other threads:[~2002-10-24 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 0:36 Mark Mitchell
2002-10-24 0:43 ` Joe Buck
2002-10-24 11:39 ` Joel Sherrill
2002-10-24 15:55 ` Peter Barada
2002-10-25 6:51 ` Benjamin Kosnik [this message]
2002-11-01 7:05 ` Richard Earnshaw
2002-11-01 10:40 ` Joe Buck
2002-11-01 10:48 ` David Edelsohn
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=20021024154824.652060c1.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mark@codesourcery.com \
--cc=nickc@redhat.com \
--cc=rearnsha@arm.com \
--cc=rth@redhat.com \
/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).