Re: git fetch -v not at all verbose?

From: Shawn O. Pearce <spearce@spearce.org>
Date: Jan 21, 2010, 16:18 UTC
Message-ID: <20100121161858.GC19078@spearce.org>
In-Reply-To: <20100121161016.GA16300@redhat.com>

"Michael S. Tsirkin" <mst@redhat.com> wrote:

> On many of my trees (with linux kernel), git fetch is slower than git clone.
> Even more annoyingly, it would hang sometimes for tens of minutes without any
> output, even if -v is supplied.

Ouch.  I think -v -v boosts the output to be ever more verbose,
and might actually show you something.

Show 7 quoted lines

> stracing it shows a ton of lines like the following:
> 16324 read(10, "ACK 4bbdfe65d23014f539fec4227260"..., 51) = 51
> 16324 read(10, "0037", 4)               = 4
> 16324 read(10, "ACK 322c06560fa314b04a6302ea03c0"..., 51) = 51
> 16324 read(10, "0037", 4)               = 4
> 16324 read(10, "ACK 848ea2043b128b5947851866a114"..., 51) = 51
> 16324 read(10, "0037", 4)               = 4

That's the peers trying to determine a common base.

> Is there some way to make got fetch show progress at this stage,
> or even better, can it be made faster somehow?

We shouldn't need to show progress here, we should just be faster.

Given the symptom, it sounds to me like your local repository is some 1,000s of commits ahead of the remote repository you are fetching from. Is that true?

Are you fetching from a configured remote that has tracking branches, or are you fetching through a one-shot URL pasted onto the command line?

-- 
Shawn.