From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Richard Guenther <rguenther@suse.de>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>, gcc@gcc.gnu.org
Subject: Re: GCC 4.5 Status Report (2009-09-19)
Date: Sun, 20 Sep 2009 11:53:00 -0000 [thread overview]
Message-ID: <4AB61AFB.9060903@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0909201347120.4520@zhemvz.fhfr.qr>
Richard Guenther wrote:
> On Sun, 20 Sep 2009, Dave Korn wrote:
>> BTW, why don't we call this more-flexible-stage-3 "stage 2" any more? It
>> sounds a lot like the way that's still described on develop.html.
>
> Because "New functionality may not be introduced during this period." is
> still true for this stage 3 and "support for a new language construct
> might be added in a front-end" is also not wanted.
Ah, thanks. I missed the discussion when stage 2 fell out of use, it would
be nice if someone who was there at the time added a note to develop.html - is
it an ad-hoc thing that we've just done for a couple of releases because it
made sense at the time or was there an SC decision to permanently modify the
development plan?
cheers,
DaveK
next prev parent reply other threads:[~2009-09-20 11:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 20:57 Richard Guenther
2009-09-19 22:03 ` Steven Bosscher
2009-09-19 22:22 ` Richard Guenther
2009-09-20 1:21 ` Geert Bosch
2009-09-20 1:00 ` Jack Howarth
2009-09-20 1:35 ` Dave Korn
2009-09-20 8:54 ` Richard Guenther
2009-09-20 11:38 ` Dave Korn
2009-09-20 11:48 ` Richard Guenther
2009-09-20 11:53 ` Dave Korn [this message]
2009-09-24 14:44 ` Jason Merrill
2009-09-24 14:50 ` Richard Guenther
2009-09-21 18:23 ` Cary Coutant
2009-09-21 18:57 ` Jack Howarth
2009-09-21 21:05 ` Cary Coutant
2009-09-21 21:10 ` Cary Coutant
2009-09-29 18:10 ` Sriraman Tallam
2009-09-29 22:08 ` Dave Korn
2009-09-29 22:59 ` Gerald Pfeifer
2009-09-30 10:40 ` Richard Guenther
2009-09-30 15:00 ` Jack Howarth
2009-10-01 0:17 ` Neil Vachharajani
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=4AB61AFB.9060903@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).