From: Andreas Ericsson <ae@op5.se>
To: Nicolas Pitre <nico@cam.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] nicer eye candies for pack-objects
Date: Thu, 23 Feb 2006 00:19:04 +0100 [thread overview]
Message-ID: <43FCF168.1060802@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0602221733030.5606@localhost.localdomain>
Nicolas Pitre wrote:
> On Wed, 22 Feb 2006, Junio C Hamano wrote:
>
>
>>I like this, but like the "every second or every percent
>>whichever comes first" unpack-objects does even better. How
>>about something like this on top of your patch?
>
>
> Well... my concern is (if I'm right) that this status is generated
> remotely and sent over the network when performing a fetch. The "every
> percent" might in this case generate quite some significant overhead if
> the pack is small.
>
But if the pack is small it won't matter. It's when it's big we want to
know about it (and then the each-percent method is better, really).
> Also (personal opinion) such progress numbers are harder to read when
> they change too fast.
>
I don't know about the rest of the world, but when I see numbers
counting up with a percent-sign behind them I do some mental math to see
how many brain-ticks go between each increment and then multiply with
100 to see if I need to get a beer while waiting. I don't really care
what number it shows if it flashes too fast to read.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
prev parent reply other threads:[~2006-02-22 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 21:00 [PATCH] nicer eye candies for pack-objects Nicolas Pitre
2006-02-22 22:27 ` Junio C Hamano
2006-02-22 22:37 ` Nicolas Pitre
2006-02-22 23:05 ` Linus Torvalds
2006-02-22 23:40 ` Nicolas Pitre
2006-02-22 23:19 ` Andreas Ericsson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43FCF168.1060802@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).