public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yotam Medini <yotamm@tmai.com>
To: egcs@cygnus.com
Cc: khan@xraylith.wisc.edu
Subject: egcs & gcc 2.8
Date: Wed, 10 Dec 1997 10:58:00 -0000	[thread overview]
Message-ID: <199712101809.KAA02446@telaviv.tmai.com> (raw)

> Date: Wed, 10 Dec 1997 09:31:28 -0600
> From: Mumit Khan <khan@xraylith.wisc.edu>
> 
> ...
> Things have changed quite a bit since the gcc-2.8.0 merge, and I'll
> probably make a new release after things settle down a bit.


 http://www.cygnus.com/egcs/egcs-1.0.html:

   egcs-1.0 also contains many improvements and features not found in
   gcc-2.7 and even the soon to be released gcc-2.8 compilers.

Could someone please educate me about the relations between 
egcs and gcc 2.8?

-- yotam

             reply	other threads:[~1997-12-10 10:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-10 10:58 Yotam Medini [this message]
1997-12-10 16:43 ` 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=199712101809.KAA02446@telaviv.tmai.com \
    --to=yotamm@tmai.com \
    --cc=egcs@cygnus.com \
    --cc=khan@xraylith.wisc.edu \
    /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).