Date: Fri, 16 Mar 2001 11:44:29 -0800 (PST) From: Dennis Glatting <dennis.glatting@software-munitions.com> To: <current@freebsd.org> Subject: gcc-2.95.3 is released. (fwd) Message-ID: <Pine.BSF.4.31.0103161144140.30123-100000@btw.plaintalk.bellevue.wa.us>
next in thread | raw e-mail | index | archive | help
FYI ---------- Forwarded message ---------- Date: Fri, 16 Mar 2001 15:52:00 +0000 (GMT) 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. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.31.0103161144140.30123-100000>