git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/2] Dealing with a lot of submodules

From
Stefan Beller <sbeller@google.com>
Date
Jun 9, 2016, 19:06 UTC
Message-ID
<20160609190637.21177-1-sbeller@google.com>

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
Next: Stefan Beller
Message 1 of 8 in “Dealing with a lot of submodules”
  1. 0/2 Dealing with a lot of submodulesStefan Beller, Jun 9, 2016
  2. 1/2 submodule--helper: initial clone learns retry logicStefan Beller, Jun 9, 2016
  3. Junio C HamanoJun 9, 2016
  4. Stefan BellerJun 9, 2016
  5. Junio C HamanoJun 9, 2016
  6. Junio C HamanoJun 9, 2016
  7. Stefan BellerJun 9, 2016
  8. 2/2 submodule update: continue when a clone failsStefan Beller, Jun 9, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.