From: Daniel Barkalow <barkalow@iabervon.org>
To: David Brownell <david-b@pacbell.net>
Cc: git@vger.kernel.org
Subject: Re: warning: no common commits - slow pull
Date: Fri, 7 Mar 2008 20:22:01 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.1.00.0803072006550.19665@iabervon.org> (raw)
In-Reply-To: <200803061735.47674.david-b@pacbell.net>
On Thu, 6 Mar 2008, David Brownell wrote:
> Any progress on fixing this?
>
> I'll report that with git version 1.5.4.3.447.gc95b3.dirty
> (just a couple days old) I've observed this when updating
> a clone by pulling from
>
> (a) a parent on the same disk partition
> (b) a parent on a non-mirrored network server
>
> So that would seem to trash the assumptions that this is
> related to version mismatch between mirrors, and that the
> fix can (or should!) wait till 1.6.0 ...
>
> I was glad to see the "^C" workaround, that seems to work.
>
> When I "git pull" it first fetches a bunch of files, then
> concludes (wrongly) "no common commits", then starts a
> second fetch of a *HUGE* number of files ... 400 MB is too
> much to pay when updating from rc3-last-week to rc4. But
> if I interrupt that second one with ^C, it seems that the
> first one fetched enough to make the next "git pull" go
> pretty quickly.
>
>
> This does seem appear to show up more often lately because
> of RC4 having been tagged ... but I don't know for sure.
>
> I've got a couple kernel workspaces still on last Friday's
> version, which -- if this holds true to form! -- will show
> this bug when I "git pull". So if there are experiments
> that would help nail down what's going on here, please
> spell them out to me ("this command, then this ... send
> this output...").
Actually, if you can make a tarball of the .git directory of one of those
workspaces, and see if the bug is reproducable with that .git directory
every time (particularly when pulling a local repository), it would be
really helpful to have a reliable test case.
There's a debugging thing that would help, but it's not in your version.
It's in next as
49aaddd102aff Teach upload-pack to log the received need lines to an fd
With that commit, you should be able to do:
GIT_DEBUG_SEND_PACK=3 git pull 3>UPLOAD_LOG
and get a file UPLOAD_LOG that will show what it's doing, although there's
a reasonable chance that it'll only demonstrate that it's doing nothing
helpful, which we already pretty much know.
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2008-03-08 1:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 1:35 warning: no common commits - slow pull David Brownell
2008-03-08 1:22 ` Daniel Barkalow [this message]
2008-03-08 22:48 ` David Brownell
2008-03-08 22:58 ` Daniel Barkalow
2008-03-08 23:25 ` David Brownell
2008-03-08 23:27 ` Daniel Barkalow
2008-03-09 18:47 ` Daniel Barkalow
2008-03-10 17:18 ` David Brownell
2008-03-10 17:40 ` Daniel Barkalow
-- strict thread matches above, loose matches on Subject: below --
2008-02-11 1:07 Len Brown
2008-02-11 1:44 ` Junio C Hamano
2008-02-17 3:52 ` Daniel Barkalow
2008-02-17 14:57 ` Johannes Schindelin
2008-02-17 17:46 ` Daniel Barkalow
2008-02-17 17:54 ` Junio C Hamano
2008-02-17 19:27 ` Johannes Schindelin
2008-02-17 20:41 ` Daniel Barkalow
2008-02-11 1:53 ` Theodore Tso
2008-02-11 2:39 ` Len Brown
2008-02-11 2:49 ` Junio C Hamano
2008-02-11 3:55 ` Theodore Tso
2008-02-15 21:43 ` Len Brown
2008-02-16 21:22 ` Johannes Schindelin
2008-02-25 21:59 ` Florian Weimer
2008-02-25 23:32 ` Daniel Barkalow
2008-02-26 19:38 ` Len Brown
2008-02-26 20:47 ` Nicolas Pitre
2008-02-26 23:45 ` Daniel Barkalow
2008-02-27 5:12 ` Junio C Hamano
2008-02-27 6:29 ` Junio C Hamano
2008-02-27 19:28 ` Daniel Barkalow
2008-02-27 20:53 ` Junio C Hamano
2008-02-27 21:26 ` Daniel Barkalow
2008-02-28 0:43 ` Shawn O. Pearce
2008-02-28 8:50 ` Shawn O. Pearce
2008-02-29 14:44 ` Jon Loeliger
2008-02-29 17:14 ` Daniel Barkalow
2008-02-28 0:47 ` Junio C Hamano
2008-02-28 15:53 ` Daniel Barkalow
2008-02-28 17:52 ` Junio C Hamano
2008-02-28 18:36 ` Daniel Barkalow
2008-02-11 15:54 ` Florian Weimer
2008-02-11 21:13 ` Nix
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.1.00.0803072006550.19665@iabervon.org \
--to=barkalow@iabervon.org \
--cc=david-b@pacbell.net \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).