From: Jeff King <peff@peff.net>
To: oldb0t@ro.ru
Cc: Tomas Carnecky <tomas.carnecky@gmail.com>, git@vger.kernel.org
Subject: Re: Git stops forever while cloning remote repo
Date: Wed, 4 Apr 2012 17:07:07 -0400 [thread overview]
Message-ID: <20120404210707.GA5054@sigill.intra.peff.net> (raw)
In-Reply-To: <805073108.1332078446.170729064.12423@mcgi-wr-20.rambler.ru>
On Sun, Mar 18, 2012 at 05:47:26PM +0400, oldb0t@ro.ru wrote:
> I try to clone https://github.com/angband/angband.git locally, and
> git stops in the middle, again and again, in different places. For
> instance, one time it was 38% of full repo, and another time it was
> 4% of depth 1 shallow clone. Once it stopped, it doesn't try to
> continue anymore, just get stuk forever. My internet connection is
> fine, all other works perfect: wget, browsers, mail client.
I tried to reproduce this here, but it works fine for me. Have you tried
cloning from git://github.com/angband/angband.git instead? If that works
better, that would give us a data point about where the problem is.
> Is there any way to force git to retry the connection? Something like
> wget does with -t and -T options. I use git 1.7.9.1 from Debian
> testing.
Unfortunately, no. Because the packs are generated on the fly, resuming
is tricky. One solution is to create static "bundles" that are
resumable, but not every service (nor most, really) does that[1].
However, you can try Tomas's bundler service, which will generate a
resumable bundle for you:
https://bundler.caurea.org/
-Peff
[1] I hope to eventually have GitHub do this itself, but right now the
client side of it is very manual. I have some patches in the works
to make this happen transparently if the server advertises a bundle
mirror.
next prev parent reply other threads:[~2012-04-04 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 13:47 Git stops forever while cloning remote repo oldb0t
2012-04-04 21:07 ` Jeff King [this message]
2012-04-13 18:35 ` oldb0t
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=20120404210707.GA5054@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=oldb0t@ro.ru \
--cc=tomas.carnecky@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.