fetch doc: update introductory part for clarity
- "Branches" is a more common way to say "heads" in these days. - Remote-tracking branches are used a lot more these days and it is worth mentioning that it is one of the primary side effects of the command to update them. - Avoid "X. That means Y." If Y is easier to understand to readers, just say that upfront. - Use of explicit refspec to fetch tags does not have much to do with turning "auto following" on or off. It is a way to fetch tags that otherwise would not be fetched by auto-following. Helped-by: Marc Branchaud <marcnarc@xiplink.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
e156455ea4
commit
532845604d
@ -17,20 +17,22 @@ SYNOPSIS
|
|||||||
|
|
||||||
DESCRIPTION
|
DESCRIPTION
|
||||||
-----------
|
-----------
|
||||||
Fetches named heads or tags from one or more other repositories,
|
Fetch branches and/or tags (collectively, "refs") from one or more
|
||||||
along with the objects necessary to complete them.
|
other repositories, along with the objects necessary to complete
|
||||||
|
their histories.
|
||||||
|
|
||||||
The ref names and their object names of fetched refs are stored
|
The names of refs that are fetched, together with the object names
|
||||||
in `.git/FETCH_HEAD`. This information is left for a later merge
|
they point at, are written to `.git/FETCH_HEAD`. This information
|
||||||
operation done by 'git merge'.
|
can be used to learn what was fetched. In addition, the remote-tracking
|
||||||
|
branches are updated (see description on <refspec> below for details).
|
||||||
|
|
||||||
By default, tags are auto-followed. This means that when fetching
|
By default, any tag that points into the histories being fetched is
|
||||||
from a remote, any tags on the remote that point to objects that exist
|
also fetched; the effect is to fetch tags that
|
||||||
in the local repository are fetched. The effect is to fetch tags that
|
|
||||||
point at branches that you are interested in. This default behavior
|
point at branches that you are interested in. This default behavior
|
||||||
can be changed by using the --tags or --no-tags options, by
|
can be changed by using the --tags or --no-tags options or by
|
||||||
configuring remote.<name>.tagopt, or by using a refspec that fetches
|
configuring remote.<name>.tagopt. By using a refspec that fetches tags
|
||||||
tags explicitly.
|
explicitly, you can fetch tags that do not point into branches you
|
||||||
|
are interested in as well.
|
||||||
|
|
||||||
'git fetch' can fetch from either a single named repository,
|
'git fetch' can fetch from either a single named repository,
|
||||||
or from several repositories at once if <group> is given and
|
or from several repositories at once if <group> is given and
|
||||||
|
Loading…
Reference in New Issue
Block a user