On Mon, May 7, 2012 at 11:35 AM, Erik Faye-Lund <kusmabite@xxxxxxxxx> wrote: > On Mon, May 7, 2012 at 11:26 AM, Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote: >> Am 5/7/2012 11:09, schrieb Erik Faye-Lund: >>> When cloning a large repository over a local file-system >> ... >>> $ git clone some-repo.git some-other-repo >>> Cloning into 'some-other-repo'... <happens instantly> >>> done. <hangs for minutes> >>> $ >> ... >>> I asked git >>> to clone, and it told me it finished, only to hang around for >>> several minutes while, judging by the output, doing nothing. >> >> We have a nice "Checking out files" progress indicator. I wonder why you >> do not see it. >> > > That's a very good point, I forgot about that one. I'll investigate > that part. Just to be clear, I'm seeing this problem on version > 1.7.10.1.457.g8275905 (junio's 'master' as of right now, AFAICT) on > CentOS. I've built with: > NO_OPENSSL = YesPlease > NO_CURL = YesPlease > > "git config -l" does not reveal that any progress related > config-options are set. > It seems progress is only enabled when cloning with the verbose-flag. This is because check_updates in unpack-trees.c only enabled progress if both o->update and o->verbose_update is set, and checkout in builtin/clone.c fills in opts.verbose_update with (option_verbosity > 0). So that's that mystery. I still think the output without the verbose-flag is confusing as-is. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html