Junio C Hamano <junkio@xxxxxxx> wrote: > - We need to update the documentation to say what this new > number means. Indeed; I apologize for forgetting to do that. At this point I'll wind up resending the patch to address everything so toss what you have. > It's some number close to the number of revs since the named > tag, but not exactly. > > $ git describe --debug 65ebe634 2>&1 | head -4 > searching to describe 65ebe634 > annotated 251 v2.6.20-rc5 > annotated 427 v2.6.20-rc4 > annotated 594 v2.6.20-rc3 > $ git rev-list v2.6.20-rc5..65ebe634 | wc -l > 254 > $ git rev-list v2.6.20-rc4..65ebe634 | wc -l > 430 > > And it does not seem to be always "minus 3" either. What you skipped in the --debug output above was that we hit our internal possible tag limit (10 by default) and aborted walking the revision chain. That's why we missed 3 revs in our counting. :) We probably should make an option to enable the count, and if the count is enabled then we'll have to pickup counting where we left off and finish it out for the chosen tag so the count is correct. -- Shawn. - 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