Have you considered using an s/key-like system to make these hashes more
human-readable? Using the S/Key translation (11-bit chunks map to a 1-4
letter word), Linus' HEAD is at:
WOW-SCAN-NAVE-AUK-JILL-BASH-HI-LACE-LID-RIDE-RUSE-LINE-GLEE-WICK-A
...which is a little longer, but speaking of branch "wow-scan" (which
gives 22 bits of disambiguation) is probably less error-prone than
discussing branch '461...' (only 12 bits).
You could supercharge this algorithm by using (say)
/usr/dict/american-english-large (>2^17 words; 160 bits of hash = 10
dictionary words), or mixing upper and lower case (likely to reduce the 15
word s/key phrase to ~11 words) to give something like
RiDe-Rift-rIMe-rOSy-ScaR-sCat-ShiN-sIde-Sine-seeK-TIEd-TINT
My personal feeling is that case is likely to be dropped in casual
conversation, so speaking of branch 'wow', 'wow-scan', or 'wow-scan-nave'
is likely to be significantly more useful than trying to pronounce
mixed-cased versions of these.This is obviously a cogito issue, rather than a git-fs thing.
--scott
[More info is in RFCs 2289 and 1760, although all I'm really using from
these is the word dictionary in the appendix.]
http://www.faqs.org/rfcs/rfc1760.html
http://www.faqs.org/rfcs/rfc2289.htmlSKIMMER MKOFTEN Ft. Bragg Sabana Seca ESMERALDITE NORAD HTAUTOMAT
radar interception Pakistan BOND Kennedy postcard corporate globalization
( http://cscott.net/ )