Re: git fetch -v not at all verbose?

From: Shawn O. Pearce <spearce@spearce.org>
Date: Jan 21, 2010, 16:57 UTC
Message-ID: <20100121165737.GG19078@spearce.org>
In-Reply-To: <20100121163518.GA16466@redhat.com>

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

Show 5 quoted lines

> On Thu, Jan 21, 2010 at 08:18:58AM -0800, Shawn O. Pearce wrote:
> > "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.

...

Show 7 quoted lines

> > 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?

Yes.

Show 5 quoted lines

> > 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.

Hmm. I wonder if we should try to shortcut the commit walking in a case like this and just feed the tracking branches we already have.

-- 
Shawn.