This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC Release Delay
- To: Toon Moene <moene at knmi dot nl>
- Subject: Re: GCC Release Delay
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Mon, 18 Jun 2001 08:26:11 -0700
- cc: "jsm28 at cam dot ac dot uk" <jsm28 at cam dot ac dot uk>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
> However, the fact that something is "experimental", "prerelease" or
> "release" should be dealt with in one, single, version file.
>
Let's use my incompetence as an excuse to come up with a more foolproof
method. At the very least, updating gcc_release to handle more files
that version.c. At best, it seems to me that we could put all of these
versions in lockstep.
It makes sense for a library that we don't change (i.e., GNU readline,
if we used it) to have its own version number. But there's no real
reason for our Fortran runtime, Fortran compiler, C compiler, etc. to
have different version numbers. Can't we just make them all `3.0.1'
for the next release?
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com