git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git shallow clone branch doesn't work with recursive submodules cloning

From
Jeff King <peff@peff.net>
Date
Aug 15, 2016, 12:47 UTC
Message-ID
<20160815124725.t6bo5fv4lbbnqnfo@sigill.intra.peff.net>
In-Reply-To
<CAB-zwL2oFMBFjkkoh1EhSD7FCK_1wVV+whu8uxTKTHQKJgNzrQ@mail.gmail.com>
On Mon, Aug 15, 2016 at 03:29:14PM +0300, Arkady Shapkin wrote:
Show 5 quoted lines
> 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
Previous: Arkady ShapkinNext: Arkady Shapkin
Message 4 of 6 in “Git shallow clone branch doesn't work with recursive submodules cloning”
  1. Arkady ShapkinAug 15, 2016
  2. Jeff KingAug 15, 2016
  3. Arkady ShapkinAug 15, 2016
  4. Jeff KingAug 15, 2016
  5. Arkady ShapkinAug 15, 2016
  6. Jeff KingAug 15, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.