| commit | 9937e65d8835ee6c026892de48f993d7a524a00f | |
| author | W. Trevor King <wking@tremily.us> | |
| Sun, 26 Jan 2014 20:45:16 +0000 (26 12:45 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 24 Feb 2014 22:35:52 +0000 (24 14:35 -0800) | ||
| tree | ea5ed5bb7991190fa446adfef9c387383ad053be | treesnapshot (tar.gz zip) |
| parent | 23d25e48f5ead73c9ce233986f90791abec9f1e8 | commitdiff |
Documentation: describe 'submodule update --remote' use case
Make it clear that there is no implicit floating going on; --remote
lets you explicitly integrate the upstream branch in your current
HEAD (just like running 'git pull' in the submodule). The only
distinction with the current 'git pull' is the config location and
setting used for the upstream branch, which is hopefully clear now.
Signed-off-by: W. Trevor King <wking@tremily.us>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Make it clear that there is no implicit floating going on; --remote
lets you explicitly integrate the upstream branch in your current
HEAD (just like running 'git pull' in the submodule). The only
distinction with the current 'git pull' is the config location and
setting used for the upstream branch, which is hopefully clear now.
Signed-off-by: W. Trevor King <wking@tremily.us>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-submodule.txt | diffblobblamehistory |