From: Jeff King <peff@peff.net>
To: Arkady Shapkin <arkady.shapkin@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git shallow clone branch doesn't work with recursive submodules cloning
Date: Mon, 15 Aug 2016 08:47:26 -0400 [thread overview]
Message-ID: <20160815124725.t6bo5fv4lbbnqnfo@sigill.intra.peff.net> (raw)
In-Reply-To: <CAB-zwL2oFMBFjkkoh1EhSD7FCK_1wVV+whu8uxTKTHQKJgNzrQ@mail.gmail.com>
On Mon, Aug 15, 2016 at 03:29:14PM +0300, Arkady Shapkin wrote:
> Thank you, after updating to "2.9.3.windows.1" options "--recursive
> --depth 1" now works.
>
> But "--recursive --shallow-submodules" and "--recursive
> --shallow-submodules --depth 1" still doesn't work.
It does "work", but the server hosting your submodule may not be
configured to allow you to access the reachable-but-non-tip sha1
directly. So it's not a bug, but rather a configuration issue (and the
"fix" in v2.9.1 is to be less aggressive about enabling
shallow-submodules, since the default server configuration does not
allow it to work well).
More discussion is in:
http://public-inbox.org/git/OFE09D48F2.D1D14F49-ONC2257FD7.00280736-C2257FD7.0028245A@notes.na.collabserv.com/t/#u
-Peff
next prev parent reply other threads:[~2016-08-15 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 11:20 Git shallow clone branch doesn't work with recursive submodules cloning Arkady Shapkin
2016-08-15 12:04 ` Jeff King
2016-08-15 12:29 ` Arkady Shapkin
2016-08-15 12:47 ` Jeff King [this message]
2016-08-15 12:53 ` Arkady Shapkin
2016-08-15 13:03 ` Jeff King
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=20160815124725.t6bo5fv4lbbnqnfo@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=arkady.shapkin@gmail.com \
--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).