[PATCH] t5526: test recursive submodules when fetching moved submodules
- From
Stefan Beller <sbeller@google.com>
- Date
- Jun 14, 2018, 17:37 UTC
- Message-ID
- <20180614173730.205646-1-sbeller@google.com>
- In-Reply-To
- <20180614173107.201885-1-sbeller@google.com>
The topic merged in 0c7ecb7c311 (Merge branch 'sb/submodule-move-nested', 2018-05-08) provided support for moving nested submodules.
Remove the NEEDSWORK comment and implement the nested submodules test as the comment hinted at.
Signed-off-by: Stefan Beller <sbeller@google.com> ---
I found this when digging around for the previous patch.
Thanks, Stefan
t/t5526-fetch-submodules.sh | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/t/t5526-fetch-submodules.sh b/t/t5526-fetch-submodules.sh index 9cc4b569c05..359e03ff836 100755 --- a/t/t5526-fetch-submodules.sh +++ b/t/t5526-fetch-submodules.sh @@ -574,11 +574,7 @@ test_expect_success "fetch new commits when submodule got renamed" ' git clone . downstream_rename && ( cd downstream_rename && - git submodule update --init && -# NEEDSWORK: we omitted --recursive for the submodule update here since -# that does not work. See test 7001 for mv "moving nested submodules" -# for details. Once that is fixed we should add the --recursive option -# here. + git submodule update --init --recursive && git checkout -b rename && git mv submodule submodule_renamed && (
-- 2.18.0.rc1.244.gcf134e6275-goog