> That is true; submodule.recurse is not affecting git clone.
> This was a design decision once it was introduced, as the git clone might be
> too large. Maybe we need to revisit that decision and just clone the
> submodules if submodule.recurse is set.
>
> The problem that this bug report
> # Trying again with submodule.recurse
> git config --global submodule.recurse true
> git clone main clone4 cd clone4
> git checkout with-submodule
> # Submodule is still not automatically updated (sub folder is empty)
> # It seems like submodule.recurse does not affect git clone
That is true;
On Wed, Jun 13, 2018 at 18:19, Antoine W. Campagna wrote:
> Here is the full reproduction instructions:
Newlines got mangled, making my message hard to read. Sorry.
Here is the corrected reproduction instructions:
# Create a repository
mkdir main
cd main
git init
touch main.txt
git add main.txt
3 matches
Mail list logo
