From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: git fetch -v not at all verbose?
Date: Thu, 21 Jan 2010 08:57:37 -0800 [thread overview]
Message-ID: <20100121165737.GG19078@spearce.org> (raw)
In-Reply-To: <20100121163518.GA16466@redhat.com>
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> 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.
...
> > 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.
> > 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.
next prev parent reply other threads:[~2010-01-21 16:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 0:47 problem cloning via http since v1.6.6-rc0 Yaroslav Halchenko
2010-01-21 1:34 ` Tay Ray Chuan
2010-01-21 1:36 ` Tay Ray Chuan
2010-01-21 2:33 ` Yaroslav Halchenko
2010-01-21 4:01 ` Tay Ray Chuan
2010-01-21 4:38 ` Yaroslav Halchenko
2010-01-21 5:08 ` Ilari Liusvaara
2010-01-21 6:47 ` Tay Ray Chuan
2010-01-21 7:51 ` Tay Ray Chuan
2010-01-21 14:00 ` Yaroslav Halchenko
2010-01-21 14:41 ` [PATCH] http/remote-curl: coddle picky servers Tay Ray Chuan
2010-01-21 15:56 ` Shawn O. Pearce
2010-01-21 16:07 ` Mike Hommey
2010-01-21 16:10 ` git fetch -v not at all verbose? Michael S. Tsirkin
2010-01-21 16:18 ` Shawn O. Pearce
2010-01-21 16:35 ` Michael S. Tsirkin
2010-01-21 16:57 ` Shawn O. Pearce [this message]
2010-01-21 17:30 ` Michael S. Tsirkin
2010-01-21 17:47 ` Thomas Rast
2010-01-21 17:42 ` Junio C Hamano
2010-11-03 9:52 ` Michael S. Tsirkin
2010-11-03 16:14 ` Junio C Hamano
2010-01-21 16:20 ` [PATCH] http/remote-curl: coddle picky servers Tay Ray Chuan
2010-01-21 16:24 ` Shawn O. Pearce
2010-01-21 16:34 ` Mike Hommey
2010-01-21 16:34 ` Mike Hommey
2010-01-21 10:35 ` problem cloning via http since v1.6.6-rc0 Ilari Liusvaara
2010-01-21 11:36 ` Tay Ray Chuan
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=20100121165737.GG19078@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mst@redhat.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).