From: Florian Weimer <fw@deneb.enyo.de>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: phil@codesourcery.com, gcc@gcc.gnu.org
Subject: Re: Release numbering
Date: Mon, 30 Aug 2004 11:24:00 -0000 [thread overview]
Message-ID: <8765706gt0.fsf@deneb.enyo.de> (raw)
In-Reply-To: <10408301006.AA23682@vlsi1.ultra.nyu.edu> (Richard Kenner's message of "Mon, 30 Aug 04 06:06:39 EDT")
* Richard Kenner:
> Because the difference between the next release and this one will be *far*
> less than between 3.4 and this one. If people didn't feel this level of
> changes merited "4.0", the next level certainly wouldn't.
With the current release plan, I think 3.9 would be a good compromise
because some RTL passes still remain which hopefully can be removed
once the infrastructure on the tree level is available. 3.9 shows
that the release is a significant change from 3.4, and that it's still
work in progress in some areas (some will argue that a .0 release
indicates the same thing, of course 8-).
next prev parent reply other threads:[~2004-08-30 10:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 10:11 Richard Kenner
2004-08-30 10:45 ` Steven Bosscher
2004-08-30 11:24 ` Florian Weimer [this message]
2004-08-30 14:54 ` Jeffrey A Law
2004-08-30 14:57 ` Steven Bosscher
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 1:51 Richard Kenner
2004-08-30 1:59 ` Phil Edwards
2004-08-30 3:55 ` Gabriel Dos Reis
2004-08-30 10:04 ` Phil Edwards
2004-08-30 10:22 ` Gabriel Dos Reis
2004-08-30 18:42 ` Joseph S. Myers
2004-08-30 20:46 ` Phil Edwards
2004-08-30 20:57 ` Per Bothner
2004-08-30 21:02 ` Zack Weinberg
2004-08-30 21:49 ` Joseph S. Myers
[not found] ` <phil@codesourcery.com>
2004-08-30 14:42 ` David Edelsohn
2004-08-30 14:23 ` Robert Dewar
2004-08-30 4:10 ` Gabriel Dos Reis
2004-08-30 12:12 ` Laurent GUERBY
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=8765706gt0.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=phil@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).