From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3466 invoked by alias); 13 Jan 2004 00:47:54 -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 3459 invoked from network); 13 Jan 2004 00:47:54 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 13 Jan 2004 00:47:54 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AgCin-00026N-Ny for ; Mon, 12 Jan 2004 19:47:53 -0500 Date: Tue, 13 Jan 2004 00:47:00 -0000 From: Daniel Jacobowitz To: gcc@gcc.gnu.org Subject: Re: gcc 3.5 integration branch proposal Message-ID: <20040113004753.GB23498@nevyn.them.org> Mail-Followup-To: gcc@gcc.gnu.org References: <90200277-4301-11D8-BDBD-000A95B1F520@apple.com> <1073951351.3458.162.camel@minax.codesourcery.com> <02AF54EA-455D-11D8-B7FE-000393673036@apple.com> <200401130118.27506.s.bosscher@student.tudelft.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2004-01/txt/msg00761.txt.bz2 On Mon, Jan 12, 2004 at 04:23:30PM -0800, Ziemowit Laski wrote: > > On 12 Jan, 2004, at 16.18, Steven Bosscher wrote: > > >On Tuesday 13 January 2004 01:11, Ziemowit Laski wrote: > >>On 12 Jan, 2004, at 15.49, Mark Mitchell wrote: > >>>Apple (and some other vendors, including CodeSourcery) is in the > >>>position of doing its own release management and bug-fixing based on > >>>various versions of GCC. Therefore, having high-quality FSF releases > >>>may not make much of a difference to Apple; Apple doesn't use it > >>>directly anyhow. > >> > >>And the reason we don't is because the FSF keeps shooting down our > >>patches. > >>You just can't have it both ways. > > > >And Apple keeps ignoring existing infrastructure. I understand the > >inconvenience for you, but you should _fix_ patches, not force in. > > Please explain what you mean by 'infrastucture' and just how evil Apple > is ignoring it. Also please explain how to fix patches that were shot > down _on principle_, such as my recent AltiVec work. That's the only patch I know of that was shot down on principle. It was shot down on the same principle the last time it was proposed, too, so you can't really claim to be surprised! And then bystanders gave you constructive comments on how to make it much more non-intrusive, to the point where a revised patch might have gotten a different reaction. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer