From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28978 invoked by alias); 5 Dec 2001 18:22:45 -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 28941 invoked from network); 5 Dec 2001 18:22:43 -0000 Received: from unknown (HELO kiruna.synopsys.com) (204.176.20.18) by sources.redhat.com with SMTP; 5 Dec 2001 18:22:43 -0000 Received: from crone.synopsys.com (crone.synopsys.com [146.225.7.23]) by kiruna.synopsys.com (Postfix) with ESMTP id B0D65F2B8; Wed, 5 Dec 2001 10:22:43 -0800 (PST) Received: from atrus.synopsys.com (localhost [127.0.0.1]) by crone.synopsys.com (8.9.3+Sun/8.9.1) with ESMTP id KAA09037; Wed, 5 Dec 2001 10:22:25 -0800 (PST) From: Joe Buck Received: (from jbuck@localhost) by atrus.synopsys.com (8.9.3+Sun/8.9.1) id KAA21662; Wed, 5 Dec 2001 10:22:42 -0800 (PST) Message-Id: <200112051822.KAA21662@atrus.synopsys.com> Subject: Re: build status page problem To: janis187@us.ibm.com (Janis Johnson) Date: Wed, 05 Dec 2001 10:22:00 -0000 Cc: gcc@gcc.gnu.org In-Reply-To: <20011205101954.A1968@us.ibm.com> from "Janis Johnson" at Dec 05, 2001 10:19:54 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2001-12/txt/msg00227.txt.bz2 I wrote: > > I have an issue with > > > > http://gcc.gnu.org/gcc-3.0/buildstat.html. > > > > No distinction is made between 3.0, 3.0.1, and 3.0.2, and it's possible > > that an unnoticed regression might mean that, say, 3.0.1 builds on some > > obscure platform but 3.0.2 does not. We need to include the actual > > release number, there is no such thing as "3.0.x". Janis wrote: > The assumption is that everything on the GCC 3.0 build status page > builds with all releases of 3.0.x unless it says otherwise. So far > there's only one note otherwise, for s390-linux-gnu which is supported > beginning with 3.0.1. Sorry if this sounds like I'm picking on you ... But how are you assuring this? Do you have three success reports for each platform listed? (one each for 3.0, 3.0.1, and 3.0.2)? When 3.0.3 is released, will you then be sure to have four success reports for each?