From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: Removal of V2 code
Date: Mon, 20 Nov 2000 13:54:00 -0000 [thread overview]
Message-ID: <10011202154.AA07036@vlsi1.ultra.nyu.edu> (raw)
We're talking about other tools that depend on GCC.
One would hope they'd have the same policy: a released version of a
tool can only depend on a released version of GCC.
next reply other threads:[~2000-11-20 13:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 13:54 Richard Kenner [this message]
2000-11-20 14:59 ` Mark Mitchell
-- strict thread matches above, loose matches on Subject: below --
2000-11-20 8:55 Kaveh R. Ghazi
2000-11-20 9:47 ` law
2000-11-20 8:49 Richard Kenner
2000-11-20 11:11 ` Mark Mitchell
2000-11-19 17:40 Billinghurst, David (CRTS)
[not found] <Mark>
[not found] ` <Mitchell's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Sun,>
[not found] ` <19>
[not found] ` <Nov>
[not found] ` <2000>
[not found] ` <13:03:48>
[not found] ` <-0800>
2000-11-19 13:03 ` Mark Mitchell
2000-11-19 17:10 ` Geoff Keating
2000-11-19 17:24 ` Christopher Faylor
2000-11-19 17:56 ` Mark Mitchell
2000-11-19 20:24 ` Geoff Keating
2000-11-19 21:52 ` Mark Mitchell
2000-11-19 22:12 ` Geoff Keating
2000-11-19 22:33 ` Mark Mitchell
2000-11-20 1:07 ` Mark Mitchell
2000-11-20 2:11 ` Geoff Keating
2000-11-21 10:56 ` Mark Mitchell
2000-11-21 12:20 ` Benjamin Kosnik
2000-11-21 12:45 ` Mark Mitchell
2000-11-21 12:37 ` Geoff Keating
2000-11-21 12:47 ` Mark Mitchell
2000-11-20 2:54 ` Franz Sirl
2000-11-21 6:38 ` Franz Sirl
2000-11-21 7:26 ` Daniel Berlin
2000-11-20 0:41 ` Andrew Cagney
2000-11-20 0:55 ` Mark Mitchell
2000-11-20 3:32 ` Marc Espie
2000-11-20 5:53 ` Joseph S. Myers
2000-11-20 8:34 ` Mark Mitchell
[not found] ` <00112021562300.00259@hallo>
2000-11-20 14:58 ` Mark Mitchell
2000-11-21 14:14 ` Geoff Keating
2000-11-21 15:06 ` Mark Mitchell
2000-11-21 16:08 ` Tom Tromey
2000-11-21 21:41 ` Mark Mitchell
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=10011202154.AA07036@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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).