diff options
| author | Jens Lehmann <Jens.Lehmann@web.de> | 2012-01-24 21:49:56 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2012-01-24 22:18:18 (GMT) |
| commit | 1017c1abcb6d733e1de83eb5a1cf7e1bf4ad6aca (patch) | |
| tree | b73600700d9bbe43f66b40cb6056aba055f3be8f /git-submodule.sh | |
| parent | 0b26d1e8b29a4248d56078318fec6906e3007742 (diff) | |
| download | git-1017c1abcb6d733e1de83eb5a1cf7e1bf4ad6aca.zip git-1017c1abcb6d733e1de83eb5a1cf7e1bf4ad6aca.tar.gz git-1017c1abcb6d733e1de83eb5a1cf7e1bf4ad6aca.tar.bz2 | |
submodule add: fix breakage when re-adding a deep submodule
Since recently a submodule with name <name> has its git directory in the
.git/modules/<name> directory of the superproject while the work tree
contains a gitfile pointing there.
When the same submodule is added on a branch where it wasn't present so
far (it is not found in the .gitmodules file), the name is not initialized
from the path as it should. This leads to a wrong path entered in the
gitfile when the .git/modules/<name> directory is found, as this happily
uses the - now empty - name. It then always points only a single directory
up, even if we have a path deeper in the directory hierarchy.
Fix that by initializing the name of the submodule early in module_clone()
if module_name() returned an empty name and add a test to catch that bug.
Reported-by: Jehan Bing <jehan@orb.com>
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-submodule.sh')
| -rwxr-xr-x | git-submodule.sh | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/git-submodule.sh b/git-submodule.sh index 3adab93..9bb2e13 100755 --- a/git-submodule.sh +++ b/git-submodule.sh @@ -131,6 +131,7 @@ module_clone() gitdir= gitdir_base= name=$(module_name "$path" 2>/dev/null) + test -n "$name" || name="$path" base_path=$(dirname "$path") gitdir=$(git rev-parse --git-dir) |