From: Bernd Schmidt <bernds@cambridge.redhat.com>
To: <gcc-announce@gcc.gnu.org>
Cc: <gcc@gcc.gnu.org>
Subject: gcc-2.95.3 is released.
Date: Fri, 16 Mar 2001 08:59:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0103161438360.1311-100000@host140.cambridge.redhat.com> (raw)
gcc version 2.95.3 is now available from
ftp://gcc.gnu.org/pub/gcc/releases/gcc-2.95.3/
A more detailed announcement can be found on
http://gcc.gnu.org/gcc-2.95/gcc-2.95.3.html
If you already have test release 5, you do not need to upgrade; there have
been no changes to the code since then.
It's taken a lot longer than everyone had hoped, but at least we can be
reasonably certain that this release is a definite improvement over 2.95.2.
Thanks to everyone who tested the prereleases and sent in the results.
I'd like to ask everyone who works on OS distributions to be a bit more
careful with version numbers. If you apply patches for your release,
_please_ make sure that your patched version clearly identifies itself,
e.g. as "2.95.3 (debian)", "2.95.3 (OpenBSD)", or whatever. Please do
not increment the version number, but also do not leave the version string
unchanged. People have done strange things to gcc-2.95.2, and this has
been a source of problems while doing regression tests for gcc-2.95.3.
Bernd
reply other threads:[~2001-03-16 8:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.30.0103161438360.1311-100000@host140.cambridge.redhat.com \
--to=bernds@cambridge.redhat.com \
--cc=gcc-announce@gcc.gnu.org \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).