Hello, for your possible interest. For some time (currently with 2.9.0) know see that a single commit gives a longer hash than necessary, even though there is no ambiguity: ?0[steffen@wales ]$ git longca| awk 'BEGIN{l7=0;l8=0}\ /^[[:alnum:]]{7} /{++l7;next}\ /^[[:alnum:]]{8} /{++l8;print}\ END{print "L7 " l7 " L8 " l8}' 786d0c9c [mimepipe.2] send.c:sendpart(): force iconv(3)+ for TEXT part handlers.. L7 3364 L8 1 So it is only this single commit.. but why? ?0[steffen@wales ]$ git long1 786d0c9 786d0c9c [mimepipe.2] send.c:sendpart(): force iconv(3)+ for TEXT part handlers.. ?0[steffen@wales ]$ git long1 786d0c 786d0c9c [mimepipe.2] send.c:sendpart(): force iconv(3)+ for TEXT part handlers.. ?0[steffen@wales ]$ git long1 786d0 786d0c9c [mimepipe.2] send.c:sendpart(): force iconv(3)+ for TEXT part handlers.. ?0[steffen@wales ]$ git long1 786d 786d0c9c [mimepipe.2] send.c:sendpart(): force iconv(3)+ for TEXT part handlers.. Not really ambiguous: ?0[steffen@wales ]$ git long|cut -f1 -d' '|grep ^786 786d0c9c 786f219 Ciao! --steffen -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html