public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: Janis Johnson <janis187@us.ibm.com>, gcc@gcc.gnu.org
Subject: Re: build status page problem
Date: Wed, 05 Dec 2001 10:17:00 -0000	[thread overview]
Message-ID: <20011205101954.A1968@us.ibm.com> (raw)
In-Reply-To: <200112051801.KAA21064@atrus.synopsys.com>; from jbuck@synopsys.com on Wed, Dec 05, 2001 at 10:01:26AM -0800

On Wed, Dec 05, 2001 at 10:01:26AM -0800, Joe Buck 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".
> 

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.

I'd prefer to keep that assumption.  If there's a regression that
prevents a target from building with a particular release we can add a
note to that effect for that target.

Janis

  reply	other threads:[~2001-12-05 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 10:01 Joe Buck
2001-12-05 10:17 ` Janis Johnson [this message]
2001-12-05 10:22   ` David Edelsohn
2001-12-05 10:52     ` Janis Johnson
2001-12-09 12:52     ` Janis Johnson
2001-12-10  3:56       ` Gerald Pfeifer
2001-12-05 10:22   ` Joe Buck

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=20011205101954.A1968@us.ibm.com \
    --to=janis187@us.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.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).