From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25343 invoked by alias); 15 May 2003 15:43:01 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 25298 invoked from network); 15 May 2003 15:43:00 -0000 Received: from unknown (HELO doubledemon.codesourcery.com) (66.60.148.227) by sources.redhat.com with SMTP; 15 May 2003 15:43:00 -0000 Received: from doubledemon.codesourcery.com (doubledemon.codesourcery.com [127.0.0.1]) by doubledemon.codesourcery.com (8.12.8/8.12.8) with ESMTP id h4FFgx9X003653; Thu, 15 May 2003 08:42:59 -0700 Subject: Re: Branch created: gcc-3_3-e500-branch From: Mark Mitchell To: Kumar Gala Cc: Zack Weinberg , geoffk@geoffk.org, dje@watson.ibm.com, gcc@gcc.gnu.org, Aldy Hernandez In-Reply-To: <493B0ADC-86E3-11D7-BC42-000393DBC2E8@motorola.com> References: <493B0ADC-86E3-11D7-BC42-000393DBC2E8@motorola.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 15 May 2003 15:43:00 -0000 Message-Id: <1053013379.1553.78.camel@doubledemon.codesourcery.com> Mime-Version: 1.0 X-SW-Source: 2003-05/txt/msg01520.txt.bz2 On Thu, 2003-05-15 at 07:41, Kumar Gala wrote: > Zach, > > Thanks for the relpy. > > Mark, Geoff, David > > What is your feeling of allowing this branch to be merged back into the > 3.3 line? I feel that there are two many changes in this branch to permit its being merged back into GCC 3.3.1. The dot-releases are supposed to contain fixes for critical defects only. We have occasionally allowed new architectures to be merged in on release branches, but only when they were completely separate and therefore could not impact existing code. Yours, -- Mark Mitchell CodeSourcery, LLC mark@codesourcery.com