path: root/Documentation/git-pull.txt
diff options
authorJens Lehmann <>2011-03-06 22:14:15 (GMT)
committerJunio C Hamano <>2011-03-09 21:10:36 (GMT)
commit794a3592ad9d8a9b273f6496052bbcb46b1924ed (patch)
tree1b26e6f07bef22d7e38b89f66baa28c850f2ee4b /Documentation/git-pull.txt
parente5f522d610d34914e3fcf8b23de1b771c467196e (diff)
fetch/pull: Describe --recurse-submodule restrictions in the BUGS section
Using the --recurse-submodules option with fetch and pull might not always fetch all the submodule commits the user expects, as this will only work when the submodule is already checked out. Document that and warn that this is expected to change in the future. Signed-off-by: Jens Lehmann <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-pull.txt')
1 files changed, 9 insertions, 0 deletions
diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index c45efb3..1aad8bf 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -220,6 +220,15 @@ If you tried a pull which resulted in a complex conflicts and
would want to start over, you can recover with 'git reset'.
+Using --recurse-submodules can only fetch new commits in already checked
+out submodules right now. When e.g. upstream added a new submodule in the
+just fetched commits of the superproject the submodule itself can not be
+fetched, making it impossible to check out that submodule later without
+having to do a fetch again. This is expected to be fixed in a future git
linkgit:git-fetch[1], linkgit:git-merge[1], linkgit:git-config[1]