summaryrefslogtreecommitdiffstats
path: root/git-fetch.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2022-03-27 10:31:23 -0700
committerJunio C Hamano <gitster@pobox.com>2022-03-27 10:31:23 -0700
commit67fef49427c9457e52b6bed728023f84fd8967d4 (patch)
tree7e3db4a268775a3ab9b9dd670a3397388d646b55 /git-fetch.txt
parent14390e2aecb283765a5377385680c6baef1ed254 (diff)
downloadgit-htmldocs-67fef49427c9457e52b6bed728023f84fd8967d4.tar.gz
Autogenerated HTML docs for v2.35.1-677-gabf47
Diffstat (limited to 'git-fetch.txt')
-rw-r--r--git-fetch.txt10
1 files changed, 4 insertions, 6 deletions
diff --git a/git-fetch.txt b/git-fetch.txt
index 550c16ca6..e9d364669 100644
--- a/git-fetch.txt
+++ b/git-fetch.txt
@@ -287,12 +287,10 @@ include::transfer-data-leaks.txt[]
BUGS
----
-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 cannot 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
-version.
+Using --recurse-submodules can only fetch new commits in submodules that are
+present locally e.g. in `$GIT_DIR/modules/`. If the upstream adds a new
+submodule, that submodule cannot be fetched until it is cloned e.g. by `git
+submodule update`. This is expected to be fixed in a future Git version.
SEE ALSO
--------