From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8754 invoked by alias); 30 Sep 2009 08:49:49 -0000 Received: (qmail 8734 invoked by uid 22791); 30 Sep 2009 08:49:48 -0000 X-SWARE-Spam-Status: No, hits=-3.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from cantor2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 30 Sep 2009 08:49:43 +0000 Received: from relay1.suse.de (mail2.suse.de [195.135.221.8]) by mx2.suse.de (Postfix) with ESMTP id A25AA867E2; Wed, 30 Sep 2009 10:49:40 +0200 (CEST) Date: Wed, 30 Sep 2009 10:40:00 -0000 From: Richard Guenther To: Gerald Pfeifer Cc: Dave Korn , gcc@gcc.gnu.org, libstdc++@gcc.gnu.org Subject: Re: GCC 4.5 Status Report (2009-09-19) In-Reply-To: Message-ID: References: <4AC27D21.6020905@gmail.com> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-09/txt/msg00632.txt.bz2 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.