This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
request for assistance on outstanding bugs
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: libstdc++ at gcc dot gnu dot org
- Cc: gdr at integrable-solutions dot net, roger at eyesopen dot com, pcarlini at suse dot de
- Date: Tue, 2 Mar 2004 14:20:27 -0600
- Subject: request for assistance on outstanding bugs
- Organization: Red Hat / Chicago
- References: <403F7C67.1080701@suse.de><m3brnkwh9x.fsf@uniton.integrable-solutions.net><403F8513.7040707@suse.de><m3wu68uz8x.fsf@uniton.integrable-solutions.net><403F995C.1040008@suse.de><m3ishsux3r.fsf@uniton.integrable-solutions.net><403FA19E.7040608@suse.de><m37jy8utgk.fsf@uniton.integrable-solutions.net><403FBC14.2050509@suse.de>
Gaby:
>By the way, care of reviewing Jerry's fix for 3247, which you promised to
>do in "a day or two" back at the beginning of January?
I realize that you lost some relevant work when your laptop was stolen.
However, I'm going to ask that you try to work with Jerry to fix this
up, this week. If Jerry's patch is not acceptable, can you explain to
him, in detail, what needs to be fixed? If you don't have the time, I'd
like to check in Jerry's patch.
See:
http://gcc.gnu.org/ml/libstdc++/2004-01/msg00008.html
>And what about 13450? I think that Roger has provided the infrastructure
>that you requested, right?
OUCH!!!
Did he? Roger, can you look at this and let the libstdc++ list know your opinion?
This should be considered high priority, I think.
>And what about 8670?
I like the suggestion proposed by Martin for this. Unless a compelling
alternative arises in the next 24 hrs, I suggest checking this in.
-benjamin