From: Diego Novillo <dnovillo@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC 3.5 Status (2004-08-29)
Date: Mon, 30 Aug 2004 17:08:00 -0000 [thread overview]
Message-ID: <1093879748.22605.21.camel@localhost.localdomain> (raw)
In-Reply-To: <4132641E.3030206@codesourcery.com>
Mark has taken enough beating for the 3.5 schedule, but I think his plan
is very reasonable and I fully support it. We are currently overloaded
with new features and we need to take a breather and start stabilizing
what we have.
$NEXTRELEASE will probably not be perfect, but $NEXTRELEASE + 1 will be
pretty good and $NEXTRELEASE + 2 will be even better.
Diego.
next prev parent reply other threads:[~2004-08-30 15:29 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 23:49 Mark Mitchell
2004-08-30 0:03 ` Andrew Pinski
2004-08-30 0:33 ` Mark Mitchell
2004-08-30 0:53 ` Daniel Berlin
2004-08-30 0:25 ` Steven Bosscher
2004-08-30 0:48 ` Mark Mitchell
2004-08-30 0:57 ` Steven Bosscher
2004-08-30 1:04 ` Mark Mitchell
2004-08-30 1:12 ` Andrew Pinski
2004-08-30 1:29 ` Mark Mitchell
2004-08-30 10:11 ` Joseph S. Myers
2004-08-30 2:46 ` Giovanni Bajo
2004-08-30 3:09 ` Matt Austern
2004-08-30 13:51 ` Speeding up C++ at -O0 (Was: GCC 3.5 Status (2004-08-29)) Giovanni Bajo
2004-08-30 18:02 ` GCC 3.5 Status (2004-08-29) Joe Buck
2004-08-30 3:32 ` Gabriel Dos Reis
2004-08-30 4:11 ` Mark Mitchell
2004-08-30 4:17 ` Gabriel Dos Reis
2004-08-30 4:43 ` Mark Mitchell
2004-08-30 5:09 ` Gabriel Dos Reis
2004-08-30 5:27 ` Mark Mitchell
2004-08-30 5:30 ` Gabriel Dos Reis
2004-08-30 6:57 ` Mark Mitchell
2004-08-30 9:24 ` Steven Bosscher
2004-08-30 10:13 ` Giovanni Bajo
2004-08-30 10:26 ` Steven Bosscher
2004-08-30 16:34 ` Jan Hubicka
2004-08-30 11:02 ` Paolo Bonzini
2004-08-30 10:03 ` Steven Bosscher
2004-08-30 15:11 ` Mark Mitchell
2004-08-30 15:21 ` Jan Hubicka
2004-08-30 17:46 ` Jeffrey A Law
2004-08-30 1:09 ` Daniel Berlin
2004-08-30 1:53 ` Mark Mitchell
2004-08-30 7:34 ` Steven Bosscher
2004-08-30 8:15 ` Mark Mitchell
2004-08-30 14:16 ` Daniel Berlin
2004-08-30 15:10 ` Mark Mitchell
2004-08-30 3:03 ` Daniel Berlin
2004-08-30 3:20 ` Mark Mitchell
2004-08-31 17:35 ` Joseph S. Myers
2004-08-30 10:50 ` Dorit Naishlos
2004-08-30 15:12 ` Mark Mitchell
2004-08-30 14:26 ` Jan Hubicka
2004-08-30 15:03 ` Mark Mitchell
2004-08-30 15:05 ` Jan Hubicka
2004-08-30 17:08 ` Diego Novillo [this message]
2004-08-31 3:25 ` Devang Patel
2004-08-30 0:59 Richard Kenner
2004-08-30 4:33 Nathanael Nerode
2004-08-30 10:17 Richard Kenner
2004-08-30 14:48 ` Mark Mitchell
2004-08-30 18:08 ` Mike Stump
2004-08-30 10:44 Richard Kenner
2004-08-30 11:27 ` Laurent GUERBY
2004-08-30 13:05 ` Jakub Jelinek
2004-08-30 18:28 ` Laurent GUERBY
2004-08-30 20:04 ` Jakub Jelinek
2004-08-30 20:25 ` Laurent GUERBY
2004-08-31 5:27 ` Eric Botcazou
2004-08-31 9:42 ` Arnaud Charlet
2004-08-30 20:14 ` Florian Weimer
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=1093879748.22605.21.camel@localhost.localdomain \
--to=dnovillo@redhat.com \
--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).