Nicolas Pitre wrote:
On Thu, 11 Jan 2007, Andreas Ericsson wrote:
Shawn O. Pearce wrote:
Where we really get hit is the large number of possible tags. The
master branch is turning up 14 tags, some dating back to v1.4.1-rc1.
I do try to abort the revision list as soon as one of those tags
cannot give me a better selection than the one I have currently,
but I still had to generate a revision list to reach that point.
It could be worth skipping tags more than 6 months older than current
branch-head. That would, at least for the git case, cut the number of tags
down by a considerable amount.
This is bound to be wrong in some cases if a project is very active with
many tags, or if there was a long period of inactivity. And what would
be the benefit? Saving 250ms on git-describe output latency?
Output latency will grow with number of tags though, won't it? I was
thinking of the repo which users had reported problems fetching tags
from, as there was more than 2k tags. If my memory serves me correctly,
this report led to the packed-refs stuff.
Unless there's some bogosity going on that leads to it finding the 14
tags in the above case.
--
Andreas Ericsson andreas.ericsson@xxxxxx
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
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