From: Jeffrey A Law <law@cygnus.com>
To: drepper@cygnus.com (Ulrich Drepper)
Cc: Jason Merrill <jason@cygnus.com>, hjl@lucon.org (H.J. Lu),
egcs@cygnus.com
Subject: Re: A STL patch for egcs 1.0.2
Date: Sun, 22 Feb 1998 16:39:00 -0000 [thread overview]
Message-ID: <10096.888185601@hurl.cygnus.com> (raw)
In-Reply-To: <r24t1vi6wr.fsf@happy.cygnus.com>
In message < r24t1vi6wr.fsf@happy.cygnus.com >you write:
> Jason Merrill <jason@cygnus.com> writes:
>
> > I still think not enough people are writing threaded code to make this
> > necessary for 1.0.2.
>
> For glibc based systems where threading is working it is used a lot.
> We get lots of mails about threading and C++.
But that does necessarily not mean we need to deal with this for
1.0.2.
1.0.2 does not have to be perfect, it needs to address the most
serious problems with 1.0.1. I think we've basically done that.
So, it seems to me we need to get 1.0.2 out the door, then start
working towards a 1.1 release.
jeff
next prev parent reply other threads:[~1998-02-22 16:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-17 9:51 (1.0.2) std/bastring.h change -- Why add std/bastring.cc? Mumit Khan
1998-02-17 10:40 ` Joe Buck
[not found] ` <199802171840.KAA06006.cygnus.egcs@atrus.synopsys.com>
1998-02-17 13:54 ` Jason Merrill
1998-02-17 15:16 ` H.J. Lu
1998-02-17 23:59 ` Mumit Khan
1998-02-18 14:54 ` A STL patch for egcs 1.0.2 H.J. Lu
1998-02-18 14:54 ` (1.0.2) std/bastring.h change -- Why add std/bastring.cc? H.J. Lu
[not found] ` <m0y5H2p-00058KC.cygnus.egcs@ocean.lucon.org>
1998-02-19 10:45 ` Jason Merrill
[not found] ` <m0y5H5T-00058KC.cygnus.egcs@ocean.lucon.org>
1998-02-19 10:47 ` A STL patch for egcs 1.0.2 Jason Merrill
1998-02-19 10:47 ` H.J. Lu
1998-02-19 12:42 ` Jason Merrill
1998-02-20 12:26 ` H.J. Lu
1998-02-20 12:26 ` Jason Merrill
1998-02-20 12:26 ` H.J. Lu
1998-02-20 11:09 ` Jason Merrill
1998-02-19 14:09 ` Ulrich Drepper
1998-02-22 16:39 ` Jeffrey A Law [this message]
1998-02-23 11:00 ` H.J. Lu
1998-02-23 9:19 ` Jeffrey A Law
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=10096.888185601@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=drepper@cygnus.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=jason@cygnus.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).