-
- Downloads
Revert "Merge branch 'sb/submodule-core-worktree'"
This reverts commit 7e25437d, reversing changes made to 00624d60. v2.19.0-rc0~165^2~1 (submodule: ensure core.worktree is set after update, 2018-06-18) assumes an "absorbed" submodule layout, where the submodule's Git directory is in the superproject's .git/modules/ directory and .git in the submodule worktree is a .git file pointing there. In particular, it uses $GIT_DIR/modules/$name to find the submodule to find out whether it already has core.worktree set, and it uses connect_work_tree_and_git_dir if not, resulting in fatal: could not open sub/.git for writing The context behind that patch: v2.19.0-rc0~165^2~2 (submodule: unset core.worktree if no working tree is present, 2018-06-12) unsets core.worktree when running commands like "git checkout --recurse-submodules" to switch to a branch without the submodule. If a user then uses "git checkout --no-recurse-submodules" to switch back to a branch with the submodule and runs "git submodule update", this patch is needed to ensure that commands using the submodule directly are aware of the path to the worktree. It is late in the release cycle, so revert the whole 3-patch series. We can try again later for 2.20. Reported-by:Allan Sandfeld Jensen <allan.jensen@qt.io> Helped-by:
Stefan Beller <sbeller@google.com> Signed-off-by:
Jonathan Nieder <jrnieder@gmail.com> Signed-off-by:
Junio C Hamano <gitster@pobox.com>
Showing
- builtin/submodule--helper.c 0 additions, 26 deletionsbuiltin/submodule--helper.c
- git-submodule.sh 0 additions, 5 deletionsgit-submodule.sh
- submodule.c 0 additions, 14 deletionssubmodule.c
- submodule.h 0 additions, 2 deletionssubmodule.h
- t/lib-submodule-update.sh 2 additions, 3 deletionst/lib-submodule-update.sh
- t/t7400-submodule-basic.sh 0 additions, 5 deletionst/t7400-submodule-basic.sh
Please register or sign in to comment