public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Richard Guenther" <richard.guenther@gmail.com>
To: "Mark Mitchell" <mark@codesourcery.com>
Cc: GCC <gcc@gcc.gnu.org>
Subject: Re: GCC 4.3.0 Status Report (2007-09-04)
Date: Thu, 06 Sep 2007 08:29:00 -0000	[thread overview]
Message-ID: <84fc9c000709060129g72e9f18cu2b415da0a1dd4ea5@mail.gmail.com> (raw)
In-Reply-To: <46DE1713.6060607@codesourcery.com>

On 9/5/07, Mark Mitchell <mark@codesourcery.com> wrote:
> Summary
> =======
>
> We are closing in on Stage 3, previously announced for September 10th.
> At this point, I'm not aware of any reason to delay that date.  Are
> there any Stage 2 patches that people don't think will be submitted by
> that point?
>
> Are there Stage 1 or Stage 2 patches in need of review?  I'll do my best
> to either (a) convince someone to review them, or (b) review them myself.

There is

http://gcc.gnu.org/ml/gcc-patches/2007-08/msg01978.html

for example, which is not suitable for stage3.

Richard.

  parent reply	other threads:[~2007-09-06  8:29 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05  2:40 Mark Mitchell
2007-09-05  3:24 ` DJ Delorie
2007-09-05  3:35   ` Mark Mitchell
2007-09-05  3:50     ` DJ Delorie
2007-09-05 22:25       ` Mark Mitchell
2007-09-05 22:32         ` DJ Delorie
2007-09-06  8:29 ` Richard Guenther [this message]
2007-09-06  9:06   ` Paolo Bonzini
2007-09-06  9:12     ` Richard Guenther
2007-09-09 19:44   ` Mark Mitchell
2007-09-09 21:11     ` Roger Sayle
2007-09-09 21:19       ` Richard Guenther
2007-09-09 21:30         ` Mark Mitchell
2007-09-06  9:18 ` Manuel López-Ibáñez
2007-09-06 17:33   ` Fu, Chao-Ying
2007-09-06 12:35 ` Jan Hubicka
2007-09-09 19:45   ` Mark Mitchell
2007-09-10  1:19     ` Jan Hubicka
2007-09-06 13:38 ` Sebastian Pop
2007-09-06 17:53   ` Jagasia, Harsha
2007-09-09 19:46     ` Mark Mitchell
2007-09-10 16:04       ` Jagasia, Harsha
2007-09-07 14:50 ` Martin Jambor
2007-09-09 18:43   ` Mark Mitchell
2007-09-10 19:01     ` Martin Jambor
2007-09-25 19:49     ` Martin Jambor
2007-09-08 12:14 ` Rask Ingemann Lambertsen
2007-09-09 18:55   ` Mark Mitchell
2007-09-10 13:25 ` Jakub Jelinek
2007-09-11  3:50   ` Mark Mitchell
2007-09-12 11:02     ` Kai Tietz
2007-09-13  6:03       ` Mark Mitchell
2007-09-13  8:46         ` Jan Hubicka
2007-09-13 18:42           ` Michael Meissner
2007-09-13 22:09             ` Joseph S. Myers
2007-09-14  7:35               ` Kai Tietz
2007-09-13 18:42           ` Mark Mitchell
2007-09-14  8:04             ` Kai Tietz
2007-09-14 16:50               ` Mark Mitchell
2007-09-17  6:56                 ` Kai Tietz
2007-09-17 21:31                   ` Mark Mitchell
2007-09-10 16:20 ` Peter Bergner
2007-09-11  3:57   ` Mark Mitchell
2007-09-10 16:37 ` Michael Meissner
2007-09-13 18:37   ` Mark Mitchell
2007-09-13 18:44     ` Meissner, Michael
2007-09-13 18:48       ` Mark Mitchell
2007-09-12 12:26 ` Ramana Radhakrishnan
2007-09-13 18:39   ` 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=84fc9c000709060129g72e9f18cu2b415da0a1dd4ea5@mail.gmail.com \
    --to=richard.guenther@gmail.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).