diff options
author | Jens Lehmann <Jens.Lehmann@web.de> | 2013-08-06 23:15:11 +0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-08-07 01:10:35 +0400 |
commit | 0656781fadca17cc51fb1c30f265c251ebe12819 (patch) | |
tree | fb523dbf6f695b22ecd39809c18ded669da0715f /Documentation/git-mv.txt | |
parent | 5fee995244e13fd59500425d49038b00499396f8 (diff) |
mv: update the path entry in .gitmodules for moved submodules
Currently using "git mv" on a submodule moves the submodule's work tree in
that of the superproject. But the submodule's path setting in .gitmodules
is left untouched, which is now inconsistent with the work tree and makes
git commands that rely on the proper path -> name mapping (like status and
diff) behave strangely.
Let "git mv" help here by not only moving the submodule's work tree but
also updating the "submodule.<submodule name>.path" setting from the
.gitmodules file and stage both. This doesn't happen when no .gitmodules
file is found and only issues a warning when it doesn't have a section for
this submodule. This is because the user might just use plain gitlinks
without the .gitmodules file or has already updated the path setting by
hand before issuing the "git mv" command (in which case the warning
reminds him that mv would have done that for him). Only when .gitmodules
is found and contains merge conflicts the mv command will fail and tell
the user to resolve the conflict before trying again.
Also extend the man page to inform the user about this new feature.
Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-mv.txt')
-rw-r--r-- | Documentation/git-mv.txt | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/git-mv.txt b/Documentation/git-mv.txt index 1f6fce083e..b1f79881ef 100644 --- a/Documentation/git-mv.txt +++ b/Documentation/git-mv.txt @@ -49,6 +49,8 @@ SUBMODULES Moving a submodule using a gitfile (which means they were cloned with a Git version 1.7.8 or newer) will update the gitfile and core.worktree setting to make the submodule work in the new location. +It also will attempt to update the submodule.<name>.path setting in +the linkgit:gitmodules[5] file and stage that file (unless -n is used). GIT --- |