undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fetch --tags: clarify documentation

Browse Source 
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>
This commit is contained in:
Junio C Hamano 2012-12-13 16:19:45 -08:00
parent bdd478d620
commit f0cb2f137c
1 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Documentation/fetch-options.txt
View File

@ -57,14 +57,11 @@ endif::git-pull[]
ifndef::git-pull[] ifndef::git-pull[]
-t:: -t::
--tags:: --tags::
Most of the tags are fetched automatically as branch This is a short-hand for giving "refs/tags/*:refs/tags/*"
heads are downloaded, but tags that do not point at refspec from the command line, to ask all tags to be fetched
objects reachable from the branch heads that are being and stored locally. Because this acts as an explicit
tracked will not be fetched by this mechanism. This refspec, the default refspecs (configured with the
flag lets all tags and their associated objects be remote.$name.fetch variable) are overridden and not used.
downloaded. 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]:: --recurse-submodules[=yes|on-demand|no]::
This option controls if and under what conditions new commits of This option controls if and under what conditions new commits of