Re: [PATCH] Integrate git-version-gen.

[Jose E. Marchesi]

Hi Arsen.

> diff --git a/HACKING b/HACKING
> index 123dbc57..5325092d 100644
> --- a/HACKING
> +++ b/HACKING
> @@ -234,6 +234,21 @@ with GNU poke.  If not, see 
> <https://www.gnu.org/licenses/>.
>    The standard target `make distcheck' builds a distributable sources
>    tarball, and tests that it can be built and tested properly.
>  
> +  Note that if you're working on a checkout that is not fresh (i.e. it
> +  has had commits or tags since you last ran `./autogen.sh'), it is
> +  desirable to re-run `./autogen.sh', or otherwise regenerate
> +  `configure', to get updated version information.  This version will be
> +  stored in the newly-generated dist tarball.

So, what is the procedure to change the program version?  Right now it
is by changing the version in AC_INIT in configure.ac.

Let's see:

- If `make dist' is executed on a HEAD that has a releases/poke-X.Y[.Z]
  note in it, the version used will be "X.Y[.Z]".

- If `make dist' is executed on a HEAD that has no such tag, then the
  version used will be... what, something based on the git commit-id of
  HEAD?

> +  Keep in mind that, when regenerating, a dirty tree, including
> +  differently dated submodules, will cause the version to be suffixed
> +  with `-dirty'.

What is exactly a "dirty build"?

> +  Should this happen, and you want to go through with
> +  the release anyway, `git stash' your changes and `git submodule
> +  update' submodules, so that they get checked out to in-tree revisions.
> +  This also ensures that you're testing the version of the tree that
> +  will make it into a release, rather than something with a potentially
> +  uncommitted fix, or suchlike.

I don't understand that paragraph. "go through with the release" means
executing `make dist'?