From: Geoff Keating <geoffk@geoffk.org>
To: mark@codesourcery.com
Cc: kumar.gala@motorola.com, zack@codesourcery.com,
dje@watson.ibm.com, gcc@gcc.gnu.org, aldyh@redhat.com
Subject: Re: Branch created: gcc-3_3-e500-branch
Date: Thu, 15 May 2003 20:14:00 -0000 [thread overview]
Message-ID: <200305152014.h4FKE8M12274@desire.geoffk.org> (raw)
In-Reply-To: <1053013379.1553.78.camel@doubledemon.codesourcery.com> (message from Mark Mitchell on 15 May 2003 08:42:59 -0700)
> X-Original-To: geoffk@foam.wonderslug.com
> From: Mark Mitchell <mark@codesourcery.com>
> Cc: Zack Weinberg <zack@codesourcery.com>, geoffk@geoffk.org,
> dje@watson.ibm.com, gcc@gcc.gnu.org, Aldy Hernandez <aldyh@redhat.com>
> Date: 15 May 2003 08:42:59 -0700
> X-OriginalArrivalTime: 15 May 2003 15:43:04.0424 (UTC) FILETIME=[AC77A680:01C31AF8]
>
> 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.
I'm inclined to agree; the risks of integrating it into the 3.3
release outweigh the relativly small cost of simply keeping it on the
gcc-3_3-e500-branch during the GCC 3.3 life cycle.
--
- Geoffrey Keating <geoffk@geoffk.org>
next prev parent reply other threads:[~2003-05-15 20:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 22:07 Zack Weinberg
2003-04-16 1:15 ` Kumar Gala
2003-04-16 1:16 ` Zack Weinberg
2003-04-16 9:25 ` Kumar Gala
2003-04-16 16:09 ` Aldy Hernandez
2003-04-16 16:15 ` Kumar Gala
2003-04-16 16:50 ` Aldy Hernandez
2003-04-16 22:19 ` Jan Hubicka
2003-04-17 4:54 ` Zack Weinberg
2003-04-17 16:46 ` Aldy Hernandez
2003-04-17 17:28 ` Zack Weinberg
2003-05-15 4:10 ` Kumar Gala
2003-05-15 4:38 ` Zack Weinberg
2003-05-15 14:41 ` Kumar Gala
2003-05-15 15:43 ` Mark Mitchell
2003-05-15 20:14 ` Geoff Keating [this message]
2003-05-15 14:45 ` altivec testsuite Kumar Gala
2003-04-16 14:14 ` Branch created: gcc-3_3-e500-branch Gerald Pfeifer
2003-04-16 17:16 ` Zack Weinberg
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=200305152014.h4FKE8M12274@desire.geoffk.org \
--to=geoffk@geoffk.org \
--cc=aldyh@redhat.com \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=kumar.gala@motorola.com \
--cc=mark@codesourcery.com \
--cc=zack@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).