From: hjl@lucon.org (H.J. Lu)
To: drepper@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: libio patches for glibc 2.1
Date: Mon, 23 Feb 1998 11:00:00 -0000 [thread overview]
Message-ID: <m0y72N2-00058gC@ocean.lucon.org> (raw)
In-Reply-To: <r267m6kxvy.fsf@happy.cygnus.com>
>
> hjl@lucon.org (H.J. Lu) writes:
>
> > RedHat, Debian and SuSE may want to use egcs 1.0.x for glibc 2.1 even
> > if egcs 1.1 is released.
>
> I don't see that any of the distributions start using glibc 2.1
> sometime soon. It's the same as for egcs 1.1, they wait a bit (this is
> first hand information). Once the distribution makers consider glibc
> 2.1 we'll also have a stable egcs 1.1.
>
I, as a glibc 2.1 developer, don't want to use egcs snapshot, which
is known (intentional) to break from time to time, for glibc 2.1. I
want a stable compiler which is compatible with glibc 2.1. I don't
want another factor in my glibc 2.1 work. Other glibc 2.1
developers/testers may share the similar view with me.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-02-23 11:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-23 2:16 Andreas Schwab
1998-02-23 11:54 ` H.J. Lu
1998-02-23 11:54 ` Ulrich Drepper
1998-02-23 11:54 ` H.J. Lu
1998-02-23 11:00 ` Ulrich Drepper
1998-02-23 11:00 ` H.J. Lu [this message]
1998-02-23 11:54 ` Ulrich Drepper
1998-02-23 13:07 ` H.J. Lu
1998-02-23 14:09 ` Joe Buck
1998-02-23 15:08 ` Ulrich Drepper
1998-02-23 15:08 ` Joe Buck
1998-02-23 15:24 ` Ulrich Drepper
1998-02-23 15:31 ` Joe Buck
1998-02-23 15:34 ` Ulrich Drepper
1998-02-24 3:09 ` Jeffrey A Law
1998-02-25 9:33 ` Jeffrey A Law
1998-02-25 11:32 ` H.J. Lu
[not found] ` <1949.888379825.cygnus.egcs@hurl.cygnus.com>
1998-02-25 11:32 ` Jason Merrill
1998-02-25 19:12 ` H.J. Lu
1998-02-25 20:56 ` Jason Merrill
1998-03-05 16:38 ` H.J. Lu
1998-02-26 20:35 ` Robert Wilhelm
1998-03-05 16:38 ` H.J. Lu
1998-02-25 9:33 ` Jeffrey A Law
1998-02-23 15:57 Mike Stump
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=m0y72N2-00058gC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@cygnus.com \
--cc=egcs@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).