So it will work only if github update their server configuration (boringssl submodule on github)? 2016-08-15 15:47 GMT+03:00 Jeff King <peff@xxxxxxxx>: > 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@xxxxxxxxxxxxxxxxxxxxxxx/t/#u > > -Peff -- WBR, Arkady Shapkin aka Dragon -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html