From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Erik Faye-Lund <kusmabite@gmail.com>,
git@vger.kernel.org, peff@peff.net, rctay89@gmail.com
Subject: Re: [PATCH] clone: fix progress-regression
Date: Tue, 08 May 2012 07:46:50 +0200 [thread overview]
Message-ID: <4FA8B34A.2050204@viscovery.net> (raw)
In-Reply-To: <7vtxzr4vua.fsf@alter.siamese.dyndns.org>
Am 5/7/2012 21:47, schrieb Junio C Hamano:
> In real life, most of the checkout is fairly quick for even projects like
> the kernel, and the logic is an attempt to avoid cluttering the terminal
> with progress unless it takes unusually long and might make the user feel
> worried.
What is "unusually long"? On Windows, it can take its time to switch a
branch even if only a few dozen files are affected, the disk cache is
cold, and an on-access virus scanner is active. :-)
I appreciate the checkout progress indicator as eye candy every once in a
while.
-- Hannes
prev parent reply other threads:[~2012-05-08 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 19:23 [PATCH] clone: fix progress-regression Erik Faye-Lund
2012-05-07 19:47 ` Junio C Hamano
2012-05-08 5:46 ` Johannes Sixt [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=4FA8B34A.2050204@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kusmabite@gmail.com \
--cc=peff@peff.net \
--cc=rctay89@gmail.com \
/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).