From: Jeffrey A Law <law@cygnus.com>
To: drepper@cygnus.com (Ulrich Drepper)
Cc: hjl@lucon.org (H.J. Lu), egcs@cygnus.com
Subject: Re: libio patches for glibc 2.1
Date: Tue, 24 Feb 1998 03:09:00 -0000 [thread overview]
Message-ID: <28207.888299568@hurl.cygnus.com> (raw)
In-Reply-To: <r2en0umazz.fsf@happy.cygnus.com>
In message < r2en0umazz.fsf@happy.cygnus.com >you write:
> in more and more changes into egcs 1.0 it might not stabilize and
> especially with volatile code like the egcs/glibc 2.1 interface this
> might require even more changes once egcs 1.0.2 is out. You should
> case about Jeff who really likes to devote his time on egcs 1.1
> instead of another 1.0 release.
Exactly!
The longer we continue to work on egcs-1.0.x the longer it will be
before we can deal with egcs-1.1.
Quite a bit of my time to work on egcs is already spent on egcs-1.0.x,
and as a result work on the mainline has slowed. We need to wrap up
egcs-1.0.x then focus 100% of our effort on egcs-1.1.
jeff
next prev parent reply other threads:[~1998-02-24 3:09 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
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 [this message]
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=28207.888299568@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=drepper@cygnus.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.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).