Feature request: display build number

[GoogleCodeExporter]

With experimental builds downloaded from Google Drive, it is not always clear 
which version of the source code they have been built from (which is important 
when reporting issues or testing whether a particular issue has been resolved).

Suggestion: display the SHA1 ID of the last git commit in the Credits screen. 
See attached tutorial (this is how I implemented it in SatStat, tested on 
Eclipse, F-Droid should work but has not been tested so far).

Original issue reported on code.google.com by mich...@vonglasow.com on 25 Sep 2013 at 10:51

Attachments:

• [Show Git Build ID in Android.txt](https://storage.googleapis.com/google-code-attachments/openbmap/issue-34/comment-0/Show Git Build ID in Android.txt)

[GoogleCodeExporter]

Thanks for the script.. Unfortunately they're bash-based and the d#!$n dos 
command-line interprets the % in --pretty=format:%h as special character.

Nevertheless I hacked something together, so now the binary releases will show 
revision number in credits screen.

BTW: The resulting SHA1 ID is shorter than the Google Code's (e.g. 9463714 vs 
9463714701c9) but I assume this isn't a real problem. At least linking works 
perfectly with the short SHA1 ID, e.g. 
http://code.google.com/p/openbmap/source/detail?r=9463714

Original comment by wish7code on 25 Sep 2013 at 9:07

• Changed state: Fixed
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

yeah, Windows is a pain... glad I finally managed to get rid of it. In the 
meantime, there's also Cygwin for Windows, and git for Windows comes with a 
bash shell, too.

The actual SHA1 IDs which git uses are much longer, but usually the first few 
characters (7, 8 or 12) are sufficient to unambiguously identify a commit, 
which is why hardly anyone writes out the full SHA1, but there seem to be 
different standards on how many characters to shorten it to.

Original comment by mich...@vonglasow.com on 25 Sep 2013 at 9:44