[PATCH] Docs: Clarify the --tags option of `git fetch'
From: Michael Witten <hidden>
Date: 2016-06-15 22:52:05
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
See the discussion starting here: [PATCH] Clarify that '--tags' fetches tags only Message-ID: [ref] http://thread.gmane.org/gmane.comp.version-control.git/180636 Suggested-by: Anatol Pomozov <redacted> Signed-off-by: Michael Witten <redacted> --- Documentation/fetch-options.txt | 21 ++++++++++++++++++--- 1 files changed, 18 insertions(+), 3 deletions(-)
diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt
index 39d326a..fb743fa 100644
--- a/Documentation/fetch-options.txt
+++ b/Documentation/fetch-options.txt@@ -61,9 +61,24 @@ ifndef::git-pull[] objects reachable from the branch heads that are being tracked will not be fetched by this mechanism. This flag lets all tags and their associated objects be - downloaded. The default behavior for a remote may be - specified with the remote.<name>.tagopt setting. See - linkgit:git-config[1]. + downloaded. ++ +This option is merely a short-hand for writing the +refspec `refs/tags/\*:refs/tags/\*'; consequently, +using this option overrides any default refspec that +would be used if no refspec were provided on the +command line. That is, ++ + git fetch origin --tags + git fetch origin frotz --tags bar ++ +are equivalent to: ++ + git fetch origin 'refs/tags/*:refs/tags/*' + git fetch origin frotz 'refs/tags/*:refs/tags/*' bar ++ +The default behavior for a remote may be specified with +the remote.<name>.tagopt setting. See linkgit:git-config[1]. --recurse-submodules[=yes|on-demand|no]:: This option controls if and under what conditions new commits of
--
1.7.6.409.ge7a85