Re: [PATCH 1/2] Support for setitimer() on platforms lacking it
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 4, 2012, 18:47 UTC
- Message-ID
- <7vobllaami.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <7vwr09abim.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 16 quoted lines
> "Joachim Schmitz" <jojo@schmitz-digital.de> writes: > >>> Only with the observation of "clone", I cannot tell if your timer is >>> working. You can try repacking the test repository you created by >>> your earlier "git clone" with "git repack -a -d -f" and see what >>> happens. >> >> It does update the counter too. > > Yeah, that was not a very good way to diagnose it. > > You see the progress from pack-objects (which is the underlying > machinery "git repack" uses) only because it knows how many objects > it is going to pack, and it updates the progress meter for every > per-cent progress it makes, without any help from the timer > interrupt.
I think the "Counting objects: $number" phase is purely driven by the timer, as there is no way to say "we are done X per-cent so far".
Doesn't your repack show "Counting objects: " with a number once, pause forever and then show "Counting objects: $number, done."?