This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Add revision number to gcc version?
- From: Ben Elliston <bje at au1 dot ibm dot com>
- To: David Daney <ddaney at avtrex dot com>
- Cc: "H. J. Lu" <hjl at lucon dot org>, Mike Stump <mrs at apple dot com>, gcc at gcc dot gnu dot org
- Date: Fri, 16 Dec 2005 15:58:05 +1100
- Subject: Re: Add revision number to gcc version?
- References: <20051114171441.GA12412@lucon.org> <787EE306-43A7-4D88-B458-E39420CED0D7@apple.com> <20051114220547.GA16652@lucon.org> <20051215221609.GA25537@lucon.org> <43A1F57A.50903@avtrex.com>
> I like this, but what if you also did an svn status to see if there
> were any modifications WRT the branch/revision and then add either
> 'clean' or 'modified' to the information.
I think this is a good idea (and don't mind the idea of `svn status'
being run from gcc_update to do so), but I wonder if it's necessary to
continue to include the date in the version.c file?
I presume the main reason that the date was placed in version.c in the
first place was that we had no other way to place an overall
identifier on the tree revision with CVS. However, SVN now gives us
one. Including the date now just makes the version string unwieldly,
IMHO.
Ben