From: David Edelsohn <dje@watson.ibm.com>
To: obrien@FreeBSD.org
Cc: Bryce McKinlay <bryce@waitaki.otago.ac.nz>,
Toon Moene <toon@moene.indiv.nluug.nl>,
Neil Booth <neil@daikokuya.demon.co.uk>,
Mark Mitchell <mark@codesourcery.com>,
gcc@gcc.gnu.org
Subject: Re: GCC 3.1 Release
Date: Mon, 15 Apr 2002 18:02:00 -0000 [thread overview]
Message-ID: <200204160047.UAA30338@makai.watson.ibm.com> (raw)
In-Reply-To: Message from "David O'Brien" <obrien@FreeBSD.org> of "Mon, 15 Apr 2002 17:14:48 PDT." <20020415171448.C1064@dragon.nuxi.com>
>>>>> David O'Brien writes:
David> Waiting 18 months for the next major stable usable compiler release would
David> be hard for FreeBSD. As I mentioned, nine months is perfect for us.
I think that you misunderstood my previous message. I was not
suggesting an 18 month cycle for major stable releases. I was suggesting
that a six month cycle of releases alternating between "technology
preview" and "production" releases would require 18 months for a new,
major feature to appear in a GCC release if a proposal missed the
"technology preview" cutoff date.
David
next prev parent reply other threads:[~2002-04-16 0:51 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 18:51 Mark Mitchell
2002-04-13 2:21 ` Neil Booth
2002-04-13 7:50 ` Toon Moene
2002-04-13 8:40 ` Tim Prince
2002-04-13 23:07 ` Bryce McKinlay
2002-04-14 17:04 ` David Edelsohn
2002-04-15 17:19 ` David O'Brien
2002-04-15 18:02 ` David Edelsohn [this message]
2002-04-16 17:06 ` Marc Espie
2002-04-22 19:44 ` David O'Brien
2002-04-22 20:11 ` Bryce McKinlay
2002-04-23 11:04 ` David O'Brien
2002-04-23 16:15 ` Bryce McKinlay
2002-04-22 22:25 ` Kaveh R. Ghazi
2002-04-14 1:33 ` H . J . Lu
2002-04-16 17:00 ` Marc Espie
2002-04-17 2:08 ` Gerald Pfeifer
2002-05-17 5:42 ` Marc Espie
2002-05-17 16:19 ` Loren James Rittle
2002-05-17 17:07 ` David O'Brien
2002-05-17 17:08 ` Marc Espie
2002-04-13 13:18 ` Tom Tromey
2002-04-14 6:59 ` Jason Merrill
2002-04-14 7:25 ` Andreas Jaeger
2002-04-14 8:16 ` Jason Merrill
2002-04-15 10:56 ` Geoff Keating
2002-04-15 11:19 ` H . J . Lu
2002-04-16 15:16 ` mark
2002-04-16 15:23 ` H . J . Lu
2002-04-17 2:54 ` Andreas Schwab
2002-04-15 11:36 ` Andreas Jaeger
2002-04-15 11:37 ` Joe Buck
2002-04-15 13:13 ` Geoff Keating
2002-04-15 12:00 ` Andreas Jaeger
2002-04-15 12:01 ` Mark Mitchell
2002-04-15 12:13 ` Michael Matz
2002-04-15 12:22 ` Mark Mitchell
2002-04-15 14:52 ` Geoff Keating
2002-04-15 15:01 ` Mark Mitchell
-- strict thread matches above, loose matches on Subject: below --
2002-05-05 11:37 Mark Mitchell
2002-05-05 15:00 ` Florian Weimer
2002-05-06 3:24 ` Andreas Schwab
2002-05-06 7:54 ` Mark Mitchell
2002-05-06 7:57 ` Andreas Schwab
2002-05-06 15:16 ` Mark Mitchell
2002-05-07 1:43 ` Andreas Schwab
2002-04-15 15:06 Richard Kenner
2002-04-14 10:34 Robert Dewar
2002-04-13 13:51 Robert Dewar
2002-04-03 23:20 John David Anglin
2002-04-03 2:38 Reichelt
2002-04-03 13:21 ` Mark Mitchell
2002-04-02 14:38 Mark Mitchell
2002-04-02 14:47 ` Tom Tromey
2002-04-03 15:06 ` Phil Edwards
2002-04-03 16:08 ` Joe Buck
2002-04-03 17:57 ` Phil Edwards
2002-04-04 10:17 ` Mark Mitchell
2002-04-09 9:48 ` Joe Buck
2002-04-09 10:44 ` Benjamin Kosnik
2002-04-09 11:35 ` Gabriel Dos Reis
2002-04-10 2:37 ` Mark Mitchell
2002-04-10 7:59 ` Joe Buck
2002-04-10 8:17 ` Gabriel Dos Reis
2002-04-10 8:22 ` Joe Buck
2002-04-10 10:14 ` Mark Mitchell
2002-04-10 11:39 ` Benjamin Kosnik
2002-04-10 11:47 ` Paolo Carlini
[not found] ` <flwuvfqrme.fsf@jambon.cmla.ens-cachan.fr>
2002-04-12 5:12 ` Paolo Carlini
2002-04-10 13:01 ` Gabriel Dos Reis
2002-04-11 6:02 ` Joe Buck
2002-04-11 14:58 ` Gabriel Dos Reis
2002-04-15 17:51 ` Gabriel Dos Reis
2002-04-15 19:36 ` Gabriel Dos Reis
2002-04-15 19:43 ` Mark Mitchell
2002-04-15 20:03 ` Gabriel Dos Reis
2002-04-06 7:47 ` Jason Merrill
2002-04-10 10:17 ` Janis Johnson
2002-04-10 10:24 ` Mark Mitchell
2002-04-10 10:35 ` Christian Jönsson
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=200204160047.UAA30338@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=bryce@waitaki.otago.ac.nz \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=neil@daikokuya.demon.co.uk \
--cc=obrien@FreeBSD.org \
--cc=toon@moene.indiv.nluug.nl \
/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).