Am Wed, 23 Jun 2010 20:18:56 +0800 schrieb Holger Freyther zecke@selfish.org:
the first pointer is to the sha1/commit id[1]. So every commit has an id, it happens to be the sha1 hash over some parts of the content. Now git log will show all these as "commit". Now the openbsc version is generated by the little "./git-version-gen" utility. In fact the utility is calling "git describe" (man git-describe).
E.g. it looks like this: 0.9.0-891-gaf7edd9
0.9.0 is the last tag we had.. 891 is the number of commits since that tag gaf7edd9 is the commit/sha1. This is what you want.
I hope this helps
Unfortunately not...
I tried to give git-describe in the tree of the "sms-sending"-BSC (0.9.0-531-gb938d6b) and in the tree of the last version (0.9.0-890-g2788b96), then I tried to use git bisect:
lucabert@Luca:/tmp/bsc/openbsc$ git bisect good gb938d6b Bad rev input: gb938d6b lucabert@Luca:/tmp/bsc/openbsc$ git bisect bad g2788b96 fatal: Needed a single revision Bad rev input: g2788b96
It seems not to work... Maybe I need vacancy? I can't understand what you suppose I can do...
Thanks for your suggestion!