From: Jeff King <peff@peff.net>
To: Erik Faye-Lund <kusmabite@gmail.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Tay Ray Chuan <rctay89@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH/RFC] clone: inform the user we are checking out
Date: Mon, 7 May 2012 09:54:46 -0400 [thread overview]
Message-ID: <20120507135446.GB4860@sigill.intra.peff.net> (raw)
In-Reply-To: <CABPQNSYe6dDf20D2pQpF=K97rZnWxqe5weEdO+FdKck9rwwzWg@mail.gmail.com>
On Mon, May 07, 2012 at 12:02:46PM +0200, Erik Faye-Lund wrote:
> OK, some blaming shows that this changed in 5bd631b3 ("clone: support
> multiple levels of verbosity"), back in February 2010. Before this
> patch, one would have to specify the "quiet"-flag to clone to suppress
> progress-output, after the patch the default is progress being off.
Yeah, I think this is a bug. We already show progress indicators from
the transports without "-v", so there is no reason to require it for the
checkout progress meter. And reading fbd631b3, it looks like the change
is simply a mistake in the patch.
> This seems like the right thing to do if we want to resurrect the
> progress-output's default-on behavior:
> ---8<---
> diff --git a/builtin/clone.c b/builtin/clone.c
> index 3f863a1..f48e603 100644
> --- a/builtin/clone.c
> +++ b/builtin/clone.c
> @@ -569,7 +569,7 @@ static int checkout(void)
> opts.update = 1;
> opts.merge = 1;
> opts.fn = oneway_merge;
> - opts.verbose_update = (option_verbosity > 0);
> + opts.verbose_update = (option_verbosity >= 0);
> opts.src_index = &the_index;
> opts.dst_index = &the_index;
>
> ---8<---
Yes, that looks correct to me. Thanks for looking into this.
-Peff
next prev parent reply other threads:[~2012-05-07 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 9:09 [PATCH/RFC] clone: inform the user we are checking out Erik Faye-Lund
2012-05-07 9:26 ` Johannes Sixt
2012-05-07 9:35 ` Erik Faye-Lund
2012-05-07 9:46 ` Erik Faye-Lund
2012-05-07 10:02 ` Erik Faye-Lund
2012-05-07 13:54 ` Jeff King [this message]
2012-05-07 19:03 ` Junio C Hamano
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=20120507135446.GB4860@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=kusmabite@gmail.com \
--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).