One version number, &c, take two

[DJ Delorie]

> I don't see why those projects would ever want to have divergent
> opinions of what the current date is.

I was thinking about divergent opinions about the tagging process, not
the actual date used.  Binutils already has an alternate scheme with
daily tagging.

Um, are you planning on comitting this file daily?  The toplevel
config/* is currently manually sync'd between gcc and binutils, it
would be a mess if that blew up my scripts.

> > Plus the usual complaint about putting gcc-specific files in a shared
> > toplevel directory. 
> 
> They're not gcc-specific; they are used by several other top-level
> directories, so putting them in the gcc subdirectory is inappropriate,
> in my opinion.  Also, in the hypothetical scenario where binutils,
> gdb, etc. move to a similar scheme, I think it would be convenient to
> have all the version numbers in one place.

I meant specific to the gcc repository, as compared to gdb or
binutils, not specific to the gcc program, as compared to libstdc++ or
libiberty.