From: Richard Guenther <rguenther@suse.de>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: GCC 4.5 Status Report (2009-09-19)
Date: Wed, 30 Sep 2009 10:40:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.0909301047130.4520@zhemvz.fhfr.qr> (raw)
In-Reply-To: <alpine.LSU.1.99.0909300005190.899@acrux.dbai.tuwien.ac.at>
On Wed, 30 Sep 2009, Gerald Pfeifer wrote:
> On Tue, 29 Sep 2009, Dave Korn wrote:
> > We have ~48 hours left for stage 1 and I can't be confident of getting
> > it reviewed in the remaining time, so I'd like to make a special
> > request: can you, as RM, please say that this is OK in principle and
> > that if I can get v3 approval (it already has all other necessary
> > approvals) I can check it in during stage 3 before we branch?
>
> Historically I think we have been flexible for patches that have been
> submitted during stage 1.
>
> Now, submitting a one liner as your first attempt at a new pass today
> and then claiming the rest are just fixes, would be a stretch :-), but
> for a patch like yours it does not seem unreasonable.
Just to followup once and answer all the multiple requests that have
been (and will be) come up - during stage 3 it is up to the respective
maintainers to decide what is considered a bugfix and whether to allow
changes to go in that were submitted during stage 1. The release
managers trust the maintainers to make stage 3 a success - which means
mainly fixing fallout from stage 1 or to complete features that have
been checked in during stage 1.
Thanks,
Richard.
next prev parent reply other threads:[~2009-09-30 8:49 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
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 [this message]
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=alpine.LNX.2.00.0909301047130.4520@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=libstdc++@gcc.gnu.org \
/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).