one disadvantage of git is, that its commit-ids are ugly.
b1e7470 (even the short form of b1e74702c83accb73d60e884f7a46fc06d5d51b2) is something nobody can remember. With SVN you can say "i am using svn revision 754". a number with three to six digits for most project can be memorized.
But a commit-id of git is in the short form a seven-digit hex-number, and its "randomly" choosen (by a hash function). SVN numbers a strictly monotone, so you know the project is approximate at 750 commits, and you remember the last digit, so you can say "the commit was 754".
now i am trying something new on the otfbot
project: the ver2name function
uses the seven-digit version of a git commit-id to generate a fantasy-name.
b1e7470 → Radwalhel
now Radwalhel may be funny enough, so you can remeber it, when someone asks you, which version you are running.
The cool function about ver2name is, that it preserves all important information, so you can convert it back to a git commit-id. So the developer can use the "funny" name to find the git-revision the user is using:
Radwalhel → b1e7470some more examples:
0000000 ⇔ Babbabbab
8080808 ⇔ Mebmobmob
fffffff ⇔ Zozzazzaz
you see how its working: one hexdigit is mapping to one consonant, the 7th digit is mapping to two vocals. the third vocal is created by a hash of the last two digits, but it carries no additional information and is ignored in parsing the name back to a version.
we will see, if this helps against the confusion caused by git-commit-ids. its an experiment. And its still no solution to the problem, that two consecutive commits have totally different IDs.