From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org, gitster@pobox.com, Jens.Lehmann@web.de,
jrnieder@gmail.com, sschuberth@gmail.com
Cc: Stefan Beller <sbeller@google.com>
Subject: [PATCH 5/5] builtin/clone: Configure submodule.autoInitialize via --init-submodule
Date: Fri, 22 Jan 2016 16:31:43 -0800 [thread overview]
Message-ID: <1453509103-16470-6-git-send-email-sbeller@google.com> (raw)
In-Reply-To: <1453509103-16470-1-git-send-email-sbeller@google.com>
When invoking clone with the --init-submodule option, the choice will be
recorded in the submodule.autoInitialize config option.
Signed-off-by: Stefan Beller <sbeller@google.com>
---
Documentation/git-clone.txt | 6 +++
builtin/clone.c | 40 ++++++++++++++++--
t/t7400-submodule-basic.sh | 101 ++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 144 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 6db7b6d..4baf444 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -214,6 +214,12 @@ objects from the source repository into a pack in the cloned repository.
repository does not have a worktree/checkout (i.e. if any of
`--no-checkout`/`-n`, `--bare`, or `--mirror` is given)
+--init-submodule::
+ After the repository is cloned, specified submodules are cloned.
+ It is possible to give multiple specifications by repeating the
+ argument. This option will be recorded in the repository config
+ as `submodule.autoInitialize`.
+
--separate-git-dir=<git dir>::
Instead of placing the cloned repository where it is supposed
to be, place the cloned repository at the specified directory,
diff --git a/builtin/clone.c b/builtin/clone.c
index b004fb4..3c37c3d 100644
--- a/builtin/clone.c
+++ b/builtin/clone.c
@@ -51,6 +51,22 @@ static struct string_list option_config;
static struct string_list option_reference;
static int option_dissociate;
static int max_jobs = -1;
+static struct string_list init_submodules;
+
+static int init_submodules_cb(const struct option *opt, const char *arg, int unset)
+{
+ struct string_list_item *item;
+ struct string_list sl = STRING_LIST_INIT_DUP;
+
+ if (unset)
+ return -1;
+
+ string_list_split(&sl, arg, ',', -1);
+ for_each_string_list_item(item, &sl)
+ string_list_append((struct string_list *)opt->value, item->string);
+
+ return 0;
+}
static struct option builtin_clone_options[] = {
OPT__VERBOSITY(&option_verbosity),
@@ -95,6 +111,8 @@ static struct option builtin_clone_options[] = {
N_("separate git dir from working tree")),
OPT_STRING_LIST('c', "config", &option_config, N_("key=value"),
N_("set config inside the new repository")),
+ OPT_CALLBACK(0, "init-submodule", &init_submodules, N_("string"),
+ N_("clone specific submodules"), init_submodules_cb),
OPT_END()
};
@@ -723,9 +741,17 @@ static int checkout(void)
err |= run_hook_le(NULL, "post-checkout", sha1_to_hex(null_sha1),
sha1_to_hex(sha1), "1", NULL);
- if (!err && option_recursive) {
+ if (err)
+ goto out;
+
+ if (option_recursive || init_submodules.nr > 0) {
struct argv_array args = ARGV_ARRAY_INIT;
- argv_array_pushl(&args, "submodule", "update", "--init", "--recursive", NULL);
+ argv_array_pushl(&args, "submodule", "update", NULL);
+
+ if (option_recursive) {
+ argv_array_pushf(&args, "--init");
+ argv_array_pushf(&args, "--recursive");
+ }
if (max_jobs != -1)
argv_array_pushf(&args, "--jobs=%d", max_jobs);
@@ -733,7 +759,7 @@ static int checkout(void)
err = run_command_v_opt(args.argv, RUN_GIT_CMD);
argv_array_clear(&args);
}
-
+out:
return err;
}
@@ -867,6 +893,14 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
die(_("--bare and --separate-git-dir are incompatible."));
option_no_checkout = 1;
}
+ if (init_submodules.nr > 0) {
+ struct string_list_item *item;
+ struct strbuf sb = STRBUF_INIT;
+ for_each_string_list_item(item, &init_submodules) {
+ strbuf_addf(&sb, "submodule.autoInitialize=%s", item->string);
+ string_list_append(&option_config, strbuf_detach(&sb, 0));
+ }
+ }
if (!option_origin)
option_origin = "origin";
diff --git a/t/t7400-submodule-basic.sh b/t/t7400-submodule-basic.sh
index e1ade1e..e83f403 100755
--- a/t/t7400-submodule-basic.sh
+++ b/t/t7400-submodule-basic.sh
@@ -1064,4 +1064,105 @@ test_expect_success 'submodule update auto-initializes submodules' '
test_cmp actual expected
'
+cat <<EOF > expected
+submodule
+-submodule1
+EOF
+
+test_expect_success 'clone --init-submodule works' '
+ test_when_finished "rm -rf super super_clone" &&
+ mkdir super &&
+ pwd=$(pwd) &&
+ (
+ cd super &&
+ git init &&
+ git submodule add --label labelA file://"$pwd"/example2 submodule &&
+ git submodule add file://"$pwd"/example2 submodule1 &&
+ git commit -a -m "create repository with 2 submodules, one is in a group"
+ ) &&
+ git clone --init-submodule \*labelA super super_clone &&
+ (
+ cd super_clone &&
+ git submodule status |cut -c1,42-52 | tr -d " " >../actual
+ ) &&
+ test_cmp actual expected
+'
+
+cat <<EOF > expected
+-submodule1
+submoduleA
+-submoduleB
+submoduleC
+-submoduleD
+submoduleE
+EOF
+
+test_expect_success 'clone initializes submodules correctly with more than one --init-submodule option' '
+ test_when_finished "rm -rf super super_clone" &&
+ mkdir super &&
+ pwd=$(pwd) &&
+ (
+ cd super &&
+ git init &&
+ git submodule add --label groupA file://"$pwd"/example2 submoduleA &&
+ git submodule add --label groupB file://"$pwd"/example2 submoduleB &&
+ git submodule add --label groupC file://"$pwd"/example2 submoduleC &&
+ git submodule add --label groupD --name submoduleE file://"$pwd"/example2 submoduleD &&
+ git submodule add --label groupE --name submoduleD file://"$pwd"/example2 submoduleE &&
+ git submodule add file://"$pwd"/example2 submodule1 &&
+ git commit -a -m "create repository with submodules groups"
+ ) &&
+ git clone --init-submodule=\*groupA --init-submodule ./submoduleC --init-submodule :submoduleD super super_clone &&
+ (
+ cd super_clone &&
+ git submodule status |cut -c1,42-52 | tr -d " " >../actual
+ ) &&
+ test_cmp actual expected
+'
+
+cat <<EOF > expected1
+submoduleA
+-submoduleB
+EOF
+
+cat <<EOF > expected2
+submoduleA
+-submoduleB
+submoduleC
+EOF
+
+test_expect_success 'clone and subsequent updates correctly auto-initialize submodules' '
+ test_when_finished "rm -rf super super_clone" &&
+ mkdir super &&
+ pwd=$(pwd) &&
+ (
+ cd super &&
+ git init &&
+ git submodule add --label LA file://"$pwd"/example2 submoduleA &&
+ git submodule add file://"$pwd"/example2 submoduleB &&
+ git commit -a -m "create repository with submodules groups"
+ ) &&
+ git clone --init-submodule=\*LA super super_clone &&
+ (
+ cd super_clone &&
+ git submodule status |cut -c1,42-52 | tr -d " " >../actual
+ ) &&
+ test_cmp actual expected1 &&
+ (
+ cd super &&
+ git init &&
+ git submodule add --label LA file://"$pwd"/example2 submoduleC &&
+ git commit -a -m "add another labled submodule"
+ ) &&
+ (
+ cd super_clone &&
+ # obtain the new superproject
+ git pull &&
+ # submoduleC should just appear as it has the label LA
+ # which was configured to autoInitialize in git clone
+ git submodule update &&
+ git submodule status |cut -c1,42-52 | tr -d " " >../actual
+ ) &&
+ test_cmp actual expected2
+'
test_done
--
2.7.0.rc0.42.g77a36b9.dirty
next prev parent reply other threads:[~2016-01-23 0:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 0:31 [RFC/PATCH 0/5] [WAS: Submodule Groups] Labels and submodule.autoInitialize Stefan Beller
2016-01-23 0:31 ` [PATCH 1/5] submodule init: Write submodule registration to stderr Stefan Beller
2016-01-23 0:31 ` [PATCH 2/5] git submodule: Teach add to label submodules Stefan Beller
2016-01-23 0:31 ` [PATCH 3/5] submodule-config: keep labels around Stefan Beller
2016-01-24 18:06 ` Sebastian Schuberth
2016-01-25 18:06 ` Stefan Beller
2016-01-23 0:31 ` [PATCH 4/5] submodule update: respect submodule.autoInitialize Stefan Beller
2016-01-23 0:31 ` Stefan Beller [this message]
2016-01-24 19:38 ` [RFC/PATCH 0/5] [WAS: Submodule Groups] Labels and submodule.autoInitialize Jens Lehmann
2016-01-25 18:59 ` Stefan Beller
2016-01-26 20:59 ` Jens Lehmann
2016-01-26 21:50 ` Stefan Beller
2016-01-31 21:09 ` Jens Lehmann
2016-02-01 20:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1453509103-16470-6-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=sschuberth@gmail.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.
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 NNTP newsgroup(s).