[Gpg4win-devel] [gpg4win-2.2.6] git tag 2.2.6 contains 2.2.6-beta5
Andre Heinecke
aheinecke at intevation.de
Fri Sep 11 18:40:54 CEST 2015
Hi,
On Friday 11 September 2015 12:13:16 SERVE, OLIVIER wrote:
> I merged the gpg4win-2.2.6 tag with a local branch, and the version is now
> «2.2.6-beta5».
The Version is automatically generated and counts commits in you branch since
the last tag.
The base version is defined in configure.ac
So if you have 5 commits in your local branch that are not part of
gpg4win-2.2.6 but your configure.ac says your version is 2.2.6 this would
result in 2.2.6-beta5
In rev. ae195db1d0ee1f82ad54d8a1fb697693d63b9cc5 I've bumped the version in
the gpg4win-2 branch to 2.2.7 since then I made another commit
so my version in the gpg4win-2 branch is now: gpg4win-2.2.6-beta2
If you change the version in configure.ac you have to run ./autogen.sh --force
to get everything updated properly.
Regards,
Andre
--
Andre Heinecke | ++49-541-335083-262 | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
More information about the Gpg4win-devel
mailing list