问题
When I type git submodule update --init --recursive in order to recursively cloned submodules, it starts to say cloning... and then proceeds to do nothing... just hangs.
One apparent fix is getting the paths and repos from the .gitmodule files, navigation to the path they prescribe, and git clone them each manually.
Another apparent fix is Cntr-Z to break the action, delete the .git files that are produced by the --init clause, and trying again. It seemly works.
I seem to have a broken result however.
My main question is: is how to get git submodule update --init --recursive working property, without hanging?
Has others come across this before?
回答1:
By default, updating submodules doesn't show progress. And since many Git repos will have a relatively slow download, this can cause the appearance of hanging (and it's happened to me multiple times).
To make sure this isn't just a case of a large, slow download, run the update command with the --progress option.
git submodule update --init --recursive --progress
来源：https://stackoverflow.com/questions/45823070/git-submodule-update-init-recursive-hangs