From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] nicer eye candies for pack-objects
Date: Wed, 22 Feb 2006 17:37:06 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602221733030.5606@localhost.localdomain> (raw)
In-Reply-To: <7vy803kp1n.fsf@assigned-by-dhcp.cox.net>
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.
Also (personal opinion) such progress numbers are harder to read when
they change too fast.
Nicolas
next prev parent reply other threads:[~2006-02-22 22:37 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 [this message]
2006-02-22 23:05 ` Linus Torvalds
2006-02-22 23:40 ` Nicolas Pitre
2006-02-22 23:19 ` Andreas Ericsson
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=Pine.LNX.4.64.0602221733030.5606@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).