fetch --tags: clarify documentation
Explain that --tags is just like another explicit refspec on the command line and as such overrides the default refspecs configured via the remote.$name.fetch variable. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Dec 13, 2012 at 16:19 UTC
f0cb2f137c6e399bab1be92c7cc8e3e08bd36c4f
1 file changed
+5
-8
Documentation/fetch-options.txt
+5
-8
@@ -57,14 +57,11 @@ endif::git-pull[]
57
ifndef::git-pull[]
58
-t::
59
--tags::
60
- Most of the tags are fetched automatically as branch
61
- heads are downloaded, but tags that do not point at
62
- objects reachable from the branch heads that are being
63
- tracked will not be fetched by this mechanism. This
64
- flag lets all tags and their associated objects be
65
- downloaded. The default behavior for a remote may be
66
- specified with the remote.<name>.tagopt setting. See
67
- linkgit:git-config[1].
60
+ This is a short-hand for giving "refs/tags/*:refs/tags/*"
61
+ refspec from the command line, to ask all tags to be fetched
62
+ and stored locally. Because this acts as an explicit
63
+ refspec, the default refspecs (configured with the
64
+ remote.$name.fetch variable) are overridden and not used.
65
66
--recurse-submodules[=yes|on-demand|no]::
67
This option controls if and under what conditions new commits of