From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5822 invoked by alias); 13 Jan 2004 00:15:49 -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 5815 invoked from network); 13 Jan 2004 00:15:48 -0000 Received: from unknown (HELO mailhost2.tudelft.nl) (130.161.180.2) by sources.redhat.com with SMTP; 13 Jan 2004 00:15:48 -0000 Received: from 127.0.0.1 (localhost [127.0.0.1]) by rav.antivirus (Postfix) with SMTP id 1D30517880; Tue, 13 Jan 2004 01:15:48 +0100 (MET) Received: from listserv.tudelft.nl (listserv.tudelft.nl [130.161.180.33]) by mailhost2.tudelft.nl (Postfix) with ESMTP id 1000817879; Tue, 13 Jan 2004 01:15:48 +0100 (MET) Received: from steven.lr-s.tudelft.nl (hekje1.shuis.tudelft.nl [145.94.192.78]) by listserv.tudelft.nl (8.12.10/8.12.8) with ESMTP id i0D0FlQP008246; Tue, 13 Jan 2004 01:15:47 +0100 (MET) Received: by steven.lr-s.tudelft.nl (Postfix, from userid 500) id 3799995CA9; Tue, 13 Jan 2004 01:18:27 +0100 (CET) From: Steven Bosscher To: Ziemowit Laski , Mark Mitchell Subject: Re: gcc 3.5 integration branch proposal Date: Tue, 13 Jan 2004 00:15:00 -0000 User-Agent: KMail/1.5.4 Cc: Geoff Keating , gcc@gcc.gnu.org, Phil Edwards References: <90200277-4301-11D8-BDBD-000A95B1F520@apple.com> <1073951351.3458.162.camel@minax.codesourcery.com> <02AF54EA-455D-11D8-B7FE-000393673036@apple.com> In-Reply-To: <02AF54EA-455D-11D8-B7FE-000393673036@apple.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401130118.27506.s.bosscher@student.tudelft.nl> X-SW-Source: 2004-01/txt/msg00746.txt.bz2 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. Gr. Steven