From: Michael S. Tsirkin Date: Thu, 21 Jan 2010 16:35:18 GMT Subject: Re: git fetch -v not at all verbose? Message-ID: <20100121163518.GA16466@redhat.com> In-Reply-To: <20100121161858.GC19078@spearce.org> On Thu, Jan 21, 2010 at 08:18:58AM -0800, Shawn O. Pearce wrote: > "Michael S. Tsirkin" 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. > > > 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? Hmm, no, but what is true is that I fetched several remotes that diverged significantly into the same local repository. Would that have same effect? > 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? Configured remote. > -- > Shawn.