diff options
| author |  Junio C Hamano <gitster@pobox.com> | 2018-06-28 12:53:34 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2018-06-28 12:53:34 -0700 |
| commit | 085d2abf57be3e424cad0b7dc8c27fe41921258e (patch) | |
| tree | 758920947d1b46faf51fbfd963471c12ef5aa915 /t | |
| parent | Merge branch 'tz/cred-netrc-cleanup' (diff) | |
| parent | t5526: test recursive submodules when fetching moved submodules (diff) | |
| download | tgif-085d2abf57be3e424cad0b7dc8c27fe41921258e.tar.xz | |
Merge branch 'sb/fix-fetching-moved-submodules'
The code to try seeing if a fetch is necessary in a submodule
during a fetch with --recurse-submodules got confused when the path
to the submodule was changed in the range of commits in the
superproject, sometimes showing "(null)". This has been corrected.
* sb/fix-fetching-moved-submodules:
t5526: test recursive submodules when fetching moved submodules
submodule: fix NULL correctness in renamed broken submodules
Diffstat (limited to 't')
| -rwxr-xr-x | t/t5526-fetch-submodules.sh | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/t/t5526-fetch-submodules.sh b/t/t5526-fetch-submodules.sh index 9cc4b569c0..359e03ff83 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 && ( |