linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: linux-kernel@vger.kernel.org
Subject: Re: linux-2.2.20a and gcc 3.0 ?
Date: Sun, 4 Nov 2001 19:20:24 -0800	[thread overview]
Message-ID: <20011104192024.H267@codesourcery.com> (raw)
In-Reply-To: <3BE5EA81.6070400@stesmi.com>

> >>gcc-2.95.4 does not exist! The latest stable release is 2.95.3.
> > Ah, it does exist. You have to check it out from CVS from the GCC people.
> > I've no doubt a release will be made soon.
> 
> That's what's called a not released product.
> 
> 2.95.4 might or might not be released shortly.
> 
> It is not the final 2.95.4 that is in the CVS.
> 
> Another word for it might be BETA...

We're being extremely conservative about patches applied to the 2.95.x
CVS branch.  It is intended always to be release-quality material.

I'm not aware of any plans for an official 2.95.4 anytime soon.
However, system integrators often track that CVS branch with their GCC
packages.  For instance:

$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20011006 (Debian prerelease)

zw

  reply	other threads:[~2001-11-05  3:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-04 20:26 linux-2.2.20a and gcc 3.0 ? f5ibh
2001-11-04 20:38 ` Alan Cox
2001-11-04 22:11 ` Heinz Diehl
2001-11-04 23:13   ` Alex Buell
2001-11-05  1:25     ` Stefan Smietanowski
2001-11-05  3:20       ` Zack Weinberg [this message]
2001-11-05 13:09         ` Stefan Smietanowski
2001-11-05 20:01           ` Zack Weinberg
2001-11-05 21:03             ` Stefan Smietanowski
2001-11-05 21:45               ` Zack Weinberg
2001-11-05  9:58       ` Alex Buell
2001-11-05 11:47         ` ip autoconfig and e100 Ryan Sweet
2001-11-05 13:12         ` linux-2.2.20a and gcc 3.0 ? Stefan Smietanowski

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=20011104192024.H267@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 NNTP newsgroup(s).