summaryrefslogtreecommitdiff
path: root/Documentation/git-fetch.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2007-02-09 23:41:35 (GMT)
committerJunio C Hamano <junkio@cox.net>2007-02-09 23:41:35 (GMT)
commit02f571c73bfdf1d950848ed24229caea438f1f72 (patch)
treedd4434b55ece859cdcfd6a2deeee162cac11cce3 /Documentation/git-fetch.txt
parentad34a028c126fde97359c9d67e8d634043670a21 (diff)
downloadgit-02f571c73bfdf1d950848ed24229caea438f1f72.zip
git-02f571c73bfdf1d950848ed24229caea438f1f72.tar.gz
git-02f571c73bfdf1d950848ed24229caea438f1f72.tar.bz2
git-fetch: document automatic tag following.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/git-fetch.txt')
-rw-r--r--Documentation/git-fetch.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt
index 7ecf240..5fbeab7 100644
--- a/Documentation/git-fetch.txt
+++ b/Documentation/git-fetch.txt
@@ -20,6 +20,14 @@ The ref names and their object names of fetched refs are stored
in `.git/FETCH_HEAD`. This information is left for a later merge
operation done by "git merge".
+When <refspec> stores the fetched result in tracking branches,
+the tags that point at these branches are automatically
+followed. This is done by first fetching from the remote using
+the given <refspec>s, and if the repository has objects that are
+pointed by remote tags that it does not yet have, then fetch
+those missing tags. If the other end has tags that point at
+branches you are not interested in, you will not get them.
+
OPTIONS
-------