From: Stefan Beller <sbeller@google.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, Jens.Lehmann@web.de,
Stefan Beller <sbeller@google.com>
Subject: [PATCH 0/2] Dealing with a lot of submodules
Date: Thu, 9 Jun 2016 12:06:35 -0700 [thread overview]
Message-ID: <20160609190637.21177-1-sbeller@google.com> (raw)
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 reply other threads:[~2016-06-09 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 19:06 Stefan Beller [this message]
2016-06-09 19:06 ` [PATCH 1/2] submodule--helper: initial clone learns retry logic Stefan Beller
2016-06-09 19:19 ` Junio C Hamano
2016-06-09 19:47 ` Stefan Beller
2016-06-09 19:59 ` Junio C Hamano
2016-06-09 20:40 ` Junio C Hamano
2016-06-09 23:38 ` Stefan Beller
2016-06-09 19:06 ` [PATCH 2/2] submodule update: continue when a clone fails Stefan Beller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160609190637.21177-1-sbeller@google.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).