Re: [PATCH] git pull: Remove option handling done by fetch
From: Jonathan Nieder <hidden>
Date: 2016-06-15 22:50:31
Possibly related (same subject, not in this thread)
- 2016-06-15 · [PATCH] git pull: Remove option handling done by fetch · Jens Lehmann <hidden>
- 2016-06-15 · Re: [PATCH] git pull: Remove option handling done by fetch · Johannes Sixt <hidden>
- 2016-06-15 · Re: [PATCH] git pull: Remove option handling done by fetch · Jens Lehmann <hidden>
Jens Lehmann wrote:
2) Document "--[no-]recurse-submodules" as " as "git pull" options (And then I can later pass the same option to "git merge", which is much better than the solutions I came up with ;-)
Hmm. :) [...]
quoted hunk ↗ jump to hunk
--- a/Documentation/git-pull.txt +++ b/Documentation/git-pull.txt@@ -84,6 +84,10 @@ must be given before the options meant for 'git fetch'. --verbose:: Pass --verbose to git-fetch and git-merge. +--[no-]recurse-submodules:: + This option controls if new commits of all populated submodules should + be fetched too (see linkgit:git-config[1] and linkgit:gitmodules[5]). +
Is it worth mentioning that this does not (yet) automatically check out the new commits in submodules after a merge, or would such documentation be too likely to be forgotten and left stale in the future?