From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20368 invoked by alias); 21 Jun 2005 22:46:21 -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 20358 invoked by uid 22791); 21 Jun 2005 22:46:17 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 21 Jun 2005 22:46:17 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j5LMkG6W024031 for ; Tue, 21 Jun 2005 18:46:16 -0400 Received: from post-office.corp.redhat.com (post-office.corp.redhat.com [172.16.52.227]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j5LMkGu26060; Tue, 21 Jun 2005 18:46:16 -0400 Received: from greed.delorie.com (dj.cipe.redhat.com [10.0.0.222]) by post-office.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j5LMkFh07161; Tue, 21 Jun 2005 18:46:15 -0400 Received: from greed.delorie.com (greed.delorie.com [127.0.0.1]) by greed.delorie.com (8.13.1/8.13.1) with ESMTP id j5LMkFpT007716; Tue, 21 Jun 2005 18:46:15 -0400 Received: (from dj@localhost) by greed.delorie.com (8.13.1/8.13.1/Submit) id j5LMkAkQ007713; Tue, 21 Jun 2005 18:46:10 -0400 Date: Tue, 21 Jun 2005 22:46:00 -0000 Message-Id: <200506212246.j5LMkAkQ007713@greed.delorie.com> From: DJ Delorie To: echristo@redhat.com CC: gcc@gcc.gnu.org In-reply-to: <1119393839.16400.15.camel@dzur.sfbay.redhat.com> (message from Eric Christopher on Tue, 21 Jun 2005 15:43:59 -0700) Subject: Re: Error building 4.0.1-RC2 References: <20050620054650.GA2377@linux.comp> <1119246588.3334.9.camel@dzur.sfbay.redhat.com> <20050620061224.GA22668@linux.comp> <1119392192.16400.3.camel@dzur.sfbay.redhat.com> <200506212224.j5LMOAS4007383@greed.delorie.com> <1119393060.16400.11.camel@dzur.sfbay.redhat.com> <1119393839.16400.15.camel@dzur.sfbay.redhat.com> X-SW-Source: 2005-06/txt/msg00959.txt.bz2 > I also changed the error message to read: > > "... is not supported in this release" > > Which might work and we can, of course, remove the error message if that > ever changes :) > > OK? I have no objections, not that I'm the release manager.