From: Joe Buck <jbuck@synopsys.com>
To: hjl@lucon.org (H.J. Lu)
Cc: law@cygnus.com, egcs@cygnus.com
Subject: Re: egcs 1.0.2
Date: Sun, 15 Feb 1998 12:18:00 -0000 [thread overview]
Message-ID: <199802152017.MAA02043@atrus.synopsys.com> (raw)
In-Reply-To: <m0y46zd-0004ecC@ocean.lucon.org>
> I have 8 patches for egcs 1.0.2. I have sent 3 of them, which have
> yet to be acked. Should I send my other 5 or should I wait for
> the backlog to be cleared first?
I gather that there is controversy about spending a lot of effort to
fix "long double" in a minor release. I would think that if these
changes will not affect code that does not use long double they will
at least do no harm, and not being able to build glibc does make us
look bad.
next prev parent reply other threads:[~1998-02-15 12:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-14 23:44 egcs cvs'd between 980214 8:00 and 9:13 UTC on m68k-next-nextstep3:Success Toon Moene
1998-02-15 8:24 ` egcs cvs'd between 980214 8:00 and 9:13 UTC on m68k-next-nextstep3: Success Jeffrey A Law
1998-02-15 8:32 ` egcs 1.0.2 H.J. Lu
1998-02-15 8:33 ` Jeffrey A Law
1998-02-15 8:42 ` H.J. Lu
1998-02-15 8:46 ` Jeffrey A Law
1998-02-15 8:50 ` H.J. Lu
1998-02-15 12:18 ` Joe Buck [this message]
1998-02-15 14:04 ` H.J. Lu
1998-02-16 4:49 ` Bernd Schmidt
1998-02-16 10:34 ` H.J. Lu
1998-02-16 18:19 ` Bruno Haible
1998-02-16 13:34 Daniel Egger
1998-02-16 14:21 ` H.J. Lu
1998-03-19 20:46 Felix Morley Finch
1998-03-30 16:18 Oyvind Yrke
1998-04-01 13:41 ` Jeffrey A Law
1998-04-01 19:44 ` Jim Wilson
1998-04-03 21:52 ` Joe Buck
1998-04-03 21:52 ` Andreas Schwab
[not found] <3525297C.4A20D761@stavanger.geoquest.slb.com>
1998-04-03 21:52 ` Jim Wilson
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=199802152017.MAA02043@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=law@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).