From: Jeff King <peff@peff.net>
To: Tom <mail@tgries.de>
Cc: git@vger.kernel.org
Subject: Re: [BUG] shallow clones over http
Date: Sat, 13 Apr 2013 02:03:10 -0400 [thread overview]
Message-ID: <20130413060310.GA21921@sigill.intra.peff.net> (raw)
In-Reply-To: <loom.20130410T144700-304@post.gmane.org>
On Wed, Apr 10, 2013 at 12:48:51PM +0000, Tom wrote:
> The problem occurs to me also when I want to "deepen" a shallow clone of
> MediaWiki via https://
>
> git clone --depth 1 https://gerrit.wikimedia.org/r/p/mediawiki/core.git
> git pull --depth=99999
>
> fatal: git fetch-pack: expected shallow list.
>
> Perhaps it helps someone to find the reason.
>
> UPDATE:
>
> This however works
>
> git clone --depth=2 https://gerrit.wikimedia.org/r/p/mediawiki/core.git
> git fetch --depth=5
Yes, I experienced the same thing. I don't think the problem is related
to the depth per se, but rather the particular pattern of ACKs that
upload-pack sends based on which commits are being selected.
-Peff
next prev parent reply other threads:[~2013-04-13 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 4:03 [BUG] shallow clones over http Jeff King
2013-04-10 12:01 ` Tom
2013-04-10 12:14 ` Ramkumar Ramachandra
2013-04-10 12:48 ` Tom
2013-04-13 6:03 ` Jeff King [this message]
2013-05-08 19:12 ` Junio C Hamano
2014-02-06 12:30 ` Duy Nguyen
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=20130413060310.GA21921@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=mail@tgries.de \
/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).