This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
RFA: gold version number
- From: Cary Coutant <ccoutant at gmail dot com>
- To: Ian Lance Taylor <iant at google dot com>, Nick Clifton <nickc at redhat dot com>, Alan Modra <amodra at gmail dot com>
- Cc: Binutils <binutils at sourceware dot org>
- Date: Thu, 24 Mar 2016 17:10:47 -0700
- Subject: RFA: gold version number
- Authentication-results: sourceware.org; auth=none
I've been neglecting gold's version number, which has been stuck at
1.11 for ages. I don't really have significant changes anymore that
would trigger an obvious version number bump, but a
consistently-incremented version number would still be useful for
tracking purposes. I suppose I could just remove it and show only the
binutils version number, but I think it's probably better to keep a
version number of its own.
But what strategy should I use for incrementing it? I've thought about
bumping it just before each binutils release branch is cut, or perhaps
just after, but I'm not sure how to remind myself to do that at the
right moment.
How should the version number distinguish between a release branch
build and a trunk build? Are there any hooks built in to git or
automake that would allow commit ids or datestamps to be included
automatically in the version string?
Any advice?
-cary