Re: [PATCH v2] submodule: explain first attempt failure clearly

Jonathan Tan writes: > It is additional to what fetch prints. To make it clearer, I have > removed all mentions of "additional" from the commit message. But right > now I'm not sure if that whole section is important (since what happens > can be deduced quite easily by reading the fewer than 10 l

[PATCH v2] submodule: explain first attempt failure clearly

When cloning with --recurse-submodules a superproject with at least one submodule with HEAD pointing to an unborn branch, the clone goes something like this: Cloning into 'test'... Submodule '' () registered for path '' Cloning into ''... fatal: Couldn't fi