Re: [Gnucap-devel] autoconf-WIP branch

[al davis]

On Monday 23 September 2013, Felix Salfelder wrote:
> okay, it turns out that i can't help it. especially the
> clutter. the autotools branch is now ready for merge. even
> if it's not perfect (some modifications are pending in
> autotools-WIP), i have cleaned up as much as I can and it
> works well enough.

not quite ready but getting there.  I will see what I can do.

> the patchlev.h issue needs more thought (at least from my
> perspective). i have moved it into another branch, but it is
> pretty much independent anyway.

It really is a separate issue.  Not autoconf related AT ALL.

For now, let's do it manually.  I have always done it somewhat 
manually.  For my own non-checked-in development work I often 
change it to something else, to conclusively identify the 
nonstandard probably broken version.


What it has been:

For stable releases, the version number ..  "0.35".

For snapshots and RCS checkouts .. the checkin date and RCS 
checkin number  ....  "2013.04.23 RCS 26.138"

Gnucap is no longer using RCS, so the RCS part is now incorrect.

The equivalent of the RCS number in git looks like a random 
string, a hash code, which is not nice to look at.

The RCS number is sort of redundant because the date really 
shows the same info.

With the extra branches, they need to be identified.  This is 
important.  If I am running a WIP branch, I want to know it.

What the string should say is:
The check in date and the branch name.

Not the check out date.

For a WIP branch, I could accept just the branch name.

Ideally, I would like to see the RCS numbers come back.  I think 
"git tag" is the answer, but I need to learn more about git to 
know for sure.