submodule.c: uninitialized submodules are ignored in recursive commands
authorStefan Beller <sbeller@google.com>
Tue, 18 Apr 2017 21:37:23 +0000 (14:37 -0700)
committerJunio C Hamano <gitster@pobox.com>
Wed, 19 Apr 2017 04:18:29 +0000 (21:18 -0700)
This was an oversight when working on the working tree modifying commands
recursing into submodules.

To test for uninitialized submodules, introduce another submodule
"uninitialized_sub". Adding it via `submodule add` will activate the
submodule in the preparation area (in create_lib_submodule_repo we
setup all the things in submodule_update_repo), but the later tests
will use a new testing repo that clones the preparation repo
in which the new submodule is not initialized.

By adding it to the branch "add_sub1", which is the starting point of
all other branches, we have wide coverage.

Signed-off-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
No differences found