diff options
| author | Junio C Hamano <gitster@pobox.com> | 2013-12-12 16:55:42 -0800 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2013-12-12 16:55:42 -0800 |
| commit | 4c8f2d99229331de853716af53a6a0901b4b0d68 (patch) | |
| tree | 4b9092242d6df0a53cbfe1c91fa3c3c8ce67e05e /git-fetch.txt | |
| parent | f079f7094a3ce05d8f51729b0f0b6bf2ed594114 (diff) | |
| download | git-htmldocs-4c8f2d99229331de853716af53a6a0901b4b0d68.tar.gz | |
Autogenerated HTML docs for v1.8.5.1-163-gd7ace
Diffstat (limited to 'git-fetch.txt')
| -rw-r--r-- | git-fetch.txt | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/git-fetch.txt b/git-fetch.txt index e08a02894..10657134a 100644 --- a/git-fetch.txt +++ b/git-fetch.txt @@ -24,13 +24,13 @@ 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 remote-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. +By default, tags are auto-followed. This means that when fetching +from a remote, any tags on the remote that point to objects that exist +in the local repository are fetched. The effect is to fetch tags that +point at branches that you are interested in. This default behavior +can be changed by using the --tags or --no-tags options, by +configuring remote.<name>.tagopt, or by using a refspec that fetches +tags explicitly. 'git fetch' can fetch from either a single named repository, or from several repositories at once if <group> is given and |