It works, only I have to find a replacement for `svnversion` used in
my scripts to mark the created package. There seems to be something
similar `git describe`, but somehow it shows the value of 1397
commits, while svn was already at commit 40911. Kornel
To be precise it shows: 2.0.0-1397-g8be1845, which means that this is
the 1397th commit after the tag "2.0.0" and the abbreviated sha1 is
"8be1845".
$ git log 2.0.0 -n1
shows that 2.0.0 got tagged at revision 38559.
$ git describe origin/2.0.x
2.0.3-39-gd739408, shows that there are 39 commits in branch since 2.0.3
$ git describe origin/2.0.x --match 2.0.0
2.0.0-844-gd739408, shows there were 844 commit in branch since 2.0.0
And, 38559+1397+844 is almost 40911, but there are commits in svn that
don't have an equivalent in git. These are, e.g., commits that only
change "svn:eol-style".
$ git describe 2.0.3 -- match 2.0.0
2.0.0-805-g2b36ea4, shows that 805+39=844.
Last we can check the number of commits in the 2.0 cycle:
$ git describe 2.0.0 --match 1.6.0
1.6.0-7838-g107e105
which shows that we are at 17,8% (1397/7838) in the 2.1 cycle, which
tells me that 2.1.0 will be released in March 2015.
Vincent
