git-fetch.txt: improve description of tag auto-following
Make it clearer that tags are fetched independent of which branches were fetched from the remote in any particular fetch. (Tags are even fetched if they point at objects that are in the current repository but not reachable, which is probably a bug.) Put less emphasis on the mechanism and more on the effect of tag auto-following. Also mention the options and configuration settings that can change the tag-fetching behavior. Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Michael Haggerty committed
Oct 30, 2013 at 06:33 UTC
37f0dcbdc1585dafd81c393aa750292e8634035d
1 file changed
+7
-7
Documentation/git-fetch.txt
+7
-7
@@ -24,13 +24,13 @@ The ref names and their object names of fetched refs are stored
24
in `.git/FETCH_HEAD`. This information is left for a later merge
25
operation done by 'git merge'.
26
27
-When <refspec> stores the fetched result in remote-tracking branches,
28
-the tags that point at these branches are automatically
29
-followed. This is done by first fetching from the remote using
30
-the given <refspec>s, and if the repository has objects that are
31
-pointed by remote tags that it does not yet have, then fetch
32
-those missing tags. If the other end has tags that point at
33
-branches you are not interested in, you will not get them.
27
+By default, tags are auto-followed. This means that when fetching
28
+from a remote, any tags on the remote that point to objects that exist
29
+in the local repository are fetched. The effect is to fetch tags that
30
+point at branches that you are interested in. This default behavior
31
+can be changed by using the --tags or --no-tags options, by
32
+configuring remote.<name>.tagopt, or by using a refspec that fetches
33
+tags explicitly.
34
35
'git fetch' can fetch from either a single named repository,
36
or from several repositories at once if <group> is given and