public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@hurl.cygnus.com>
To: egcs@cygnus.com
Subject: Clarification
Date: Sun, 21 Feb 1999 15:34:00 -0000	[thread overview]
Message-ID: <7872.919640039@hurl.cygnus.com> (raw)

A minor clarification on the bootstrap requirement.

It applies to code generation and optimizer chagnes.  It does not apply
to the front-ends & cpp.  Hopefully we will not ever need to apply it to
the front-ends & cpp.

The idea is not to stop develoment, but to try and stabilize changes as they
go in so we can get a better picture of a reasonable egcs-1.2 schedule.



jeff

WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@hurl.cygnus.com>
To: egcs@cygnus.com
Subject: Clarification
Date: Sun, 28 Feb 1999 22:53:00 -0000	[thread overview]
Message-ID: <7872.919640039@hurl.cygnus.com> (raw)
Message-ID: <19990228225300.YGM0jGFhblmEK418yVPZZlpBEJ1olE3PsUKyScBW6fs@z> (raw)

A minor clarification on the bootstrap requirement.

It applies to code generation and optimizer chagnes.  It does not apply
to the front-ends & cpp.  Hopefully we will not ever need to apply it to
the front-ends & cpp.

The idea is not to stop develoment, but to try and stabilize changes as they
go in so we can get a better picture of a reasonable egcs-1.2 schedule.



jeff

             reply	other threads:[~1999-02-21 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-21 15:34 Jeffrey A Law [this message]
1999-02-28 22:53 ` Clarification Jeffrey A Law
2000-07-06  3:58 Clarification Damian Minihan
2000-07-06  4:03 ` Clarification Alexandre Oliva
2000-07-06  4:32   ` Clarification Neelakanth
2000-07-06 12:31     ` Clarification Martin v. Loewis
2000-07-06  6:42   ` Clarification Philipp Thomas
2001-02-13 13:43 Clarification Sangwan, Vikas (CORP, GEITC)
2001-02-14 17:09 ` Clarification Alexandre Oliva

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=7872.919640039@hurl.cygnus.com \
    --to=law@hurl.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).