Re: [BUG REPORT] git 2.9.0 clone --recursive fails on cloning a submodule
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Jun 21, 2016, 16:48 UTC
- Message-ID
- <CACsJy8DZ8jR=jZoC9F6k+WKr4mvZHMHtvLpT5+Mt9shX5-Wj8g@mail.gmail.com>
- In-Reply-To
- <20160619100051.GA14584@sigill.intra.peff.net>
On Sun, Jun 19, 2016 at 12:00 PM, Jeff King <peff@peff.net> wrote:
Show 6 quoted lines
> Stefan, I think it might be worth revisiting the default set by d22eb04 > to propagate shallowness from the super-project clone. In an ideal > world, we would be asking each submodule for the actual commit we are > interested in, and shallowness would not matter. But until > uploadpack.allowReachableSHA1InWant works everywhere, I suspect this is > going to be a problem.
Maybe we can pass an option to subsequent clones that say "if allow-...-sha1-in-want is advertised, do a shallow clone, otherwise fall back to full clone"?
-- Duy