Re: [PATCH] t7406: submodule.<name>.update command must not be run from .gitmodules
From: Johannes Sixt <hidden>
Date: 2017-09-26 19:47:00
Possibly related (same subject, not in this thread)
- 2017-09-27 · Re: [PATCH] t7406: submodule.<name>.update command must not be run from .gitmodules · Junio C Hamano <hidden>
- 2017-09-26 · Re: [PATCH] t7406: submodule.<name>.update command must not be run from .gitmodules · Johannes Sixt <hidden>
- 2017-09-26 · Re: [PATCH] t7406: submodule.<name>.update command must not be run from .gitmodules · Jonathan Nieder <hidden>
- 2017-09-25 · [PATCH] t7406: submodule.<name>.update command must not be run from .gitmodules · Stefan Beller <hidden>
- 2017-09-25 · Re: [PATCH] t7406: submodule.<name>.update command must not be run from .gitmodules · Jonathan Nieder <hidden>
Am 26.09.2017 um 20:54 schrieb Stefan Beller:
+test_expect_success 'submodule update - command in .gitmodules is ignored' ' + test_when_finished "git -C super reset --hard HEAD^" && + + git -C super config -f .gitmodules submodule.submodule.update "!false" && + git -C super commit -a -m "add command to .gitmodules file" && + git -C super/submodule reset --hard $submodulesha1^ && + git -C super submodule update submodule && + test_path_is_missing bad
This test for a missing file is certainly a remnant from the previous iteration, isn't it? -- Hannes