Re: [Gnucap-devel] git repo proposal

[al davis]

On Sunday 26 May 2013, Felix Salfelder wrote:
> the WIP branches are intended to stage work in progress that
> is not even final. i use this tag to indicate, that
> a) i am working on it
> b) i am waiting for comments/acceptance or merge requests
> c) i might rebase/nuke the whole thing at any time

of course.

> its definitely overkill to tamper with patchlev.h in WIP
> branches, but i agree that patchlev should be increased
> during merge into master. how about a more automatic
> approach?

The purpose of patchlev.h is so when I run the program I can see 
what it is.  Now with the library and plugins, it shows what 
library and what plugins are loaded.  Over the years, I have 
wasted lots of time trying to debug programs when the program I 
was actually running was not the one I thought it was.  Mainly 
not gnucap on this.  Rather, other programs I compiled from 
source so I could have a later version than the distro provided, 
or customize, or fix bugs.  I always make some visible change so 
I can verify which version I am running.

So if the WIP branch prints the same message as the stable one, 
I run it, how do I know that I have actually run the WIP branch?

In my old system with RCS, that was semi-automatic as part of 
the checkin target in the Makefile.  Is there a way with Git to 
have it generate some kind of string as part of the program on a 
checkin?


In my own non-released work, I do change the patchlev string, 
for these reasons.

On Sunday 26 May 2013, Felix Salfelder wrote:
> before i merge a branch into master i'll definitely remove
> the -WIP suffix (no more editing possible). how about
> fetching the branchname into patchlev.h via configure
> (unless its "master")?

That should work.  Automatic is good.