We have a test repo with about 500 submodules, and I noticed some problems when cloning this repo. This is a series that helps dealing with that repo in two ways:
* When having 500 submodules, you have to perform 500 clones. This makes an ephemeral error 500 times more likely. To cope with such errors, just try again after all other clones have finished. * If a recursive clone fails for another reason (in our case a missing .gitmodules file), we want to keep going to finish the clone, instead of failing. Thanks, Stefan Stefan Beller (2): submodule--helper: initial clone learns retry logic submodule update: continue when a clone fails builtin/submodule--helper.c | 44 ++++++++++++++++++++++++++++++++++++-------- git-submodule.sh | 2 +- 2 files changed, 37 insertions(+), 9 deletions(-) -- 2.9.0.rc2.368.gdadd65c -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
