$ git fetch <远程主机名>
$ git fetch <远程主机名> <分支名>
$ git fetch origin master
$ git branch -rorigin/master
$ git branch -a* masterremotes/origin/master
git fetch -hsage: git fetch [<options>] [<repository> [<refspec>...]]or: git fetch [<options>] <group>or: git fetch --multiple [<options>] [(<repository> | <group>)...]or: git fetch --all [<options>]-v, --verbose be more verbose-q, --quiet be more quiet--all fetch from all remotes-a, --append append to .git/FETCH_HEAD instead of overwriting--upload-pack <path> path to upload pack on remote end-f, --force force overwrite of local branch-m, --multiple fetch from multiple remotes-t, --tags fetch all tags and associated objects-n do not fetch all tags (--no-tags)-p, --prune prune remote-tracking branches no longer on remote--recurse-submodules[=<on-demand>]control recursive fetching of submodules--dry-run dry run-k, --keep keep downloaded pack-u, --update-head-ok allow updating of HEAD ref--progress force progress reporting--depth <depth> deepen history of shallow clone--unshallow convert to a complete repository--update-shallow accept refs that update .git/shallow
通过git fetch --help可以看到git fetch的语法详解。
git-fetch - Download objects and refs from another repository
git fetch [<options>] [<repository> [<refspec>…]] git fetch [<options>] <group> git fetch --multiple [<options>] [(<repository> | <group>)…] git fetch --all [<options>]
Fetches named heads or tags from on
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.
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 beha
git fetch can fetch from either a single named repository, or from several repositories at on
When no remote is specified, by default the origin remote will be used, unless there’s an upstream branch configured for the current branch.
Fetch all remotes.
Append ref names and object names of fetched refs to the existing contents of .git/FETCH_HEAD. Without this option old da
Deepen or shorten the history of a shallow repository created by git clone with --depth=<depth> option (see git-clone(1)) to the specified number of commits from the tip of each remote branch history. Tags for the deepened commits are not fetched.
If the source repository is complete, convert a shallow repository to a complete on
If the source repository is shallow, fetch as much as possible so that the current repository has the same history as the source repository.
By default when fetching from a shallow repository, git fetch refuses refs that require updating .git/shallow. This option updates .git/shallow and accept such refs.
Show what would be done, without making any changes.
When git fetch is used with <rbranch>:<lbranch> refspec, it refuses to update the local branch <lbranch> unless the remote branch <rbranch> it fetches is a descendant of <lbranch>. This option overrides that check.
Keep downloaded pack.
Allow several <repository> and <group> arguments to be specified. No <refspec>s may be specified.
After fetching, remove any remote-tracking references that no longer exist on the remote. Tags are not subject to pruning if they are fetched on
或 default tag auto-following取到本地的分支不受此控制。但是通过explicit refspec取得的tags（比如在克隆时使用了--mirror参数）也受此控制
By default, tags that point at objects that are downloaded from the remote repository are fetched and stored locally. This option disables this automatic tag following. The default beha
Fetch all tags from the remote (i.e., fetch remote tags refs/tags/* into local tags with the same name), in addition to whatever else would otherwise be fetched. Using this option alone does not subject tags to pruning, even if --prune is used (though tags may be pruned anyway if they are also the destination of an explicit refspec; see --prune).
This option controls if and under what conditions new commits of populated submodules should be fetched too. It can be used as a boolean option to completely disable recursion when set to no or to unconditionally recurse into all populated submodules when set to yes, which is the default when this option is used without any value. Use on-demand to on
Disable recursive fetching of submodules (this has the same effect as using the --recurse-submodules=no option).
Prepend <path> to paths printed in informative messages such as "Fetching submodule foo". This option is used internally when recursing over submodules.
This option is used internally to temporarily provide a non-negative default value for the --recurse-submodules option. All other methods of configuring fetch’s submodule recursion (such as settings in gitmodules(5) and git-config(1)) override this option, as does specifying --[no-]recurse-submodules directly.
By default git fetch refuses to update the head which corresponds to the current branch. This flag disables the check. This is purely for the internal use for git pull to communicate with git fetch, and unless you are implementing your own Porcelain you are not supposed to use it.
When given, and the repository to fetch from is handled by git fetch-pack, --exec=<upload-pack> is passed to the command to specify non-default path for the command run on the other end.
Pass --quiet to git-fetch-pack and silence any other internally used git commands. Progress is not reported to the standard error stream.
Progress status is reported on the standard error stream by default when it is attached to a terminal, unless -q is specified. This flag forces progress status even if the standard error stream is not directed to a terminal.
The "remote" repository that is the source of a fetch or pull operation. This parameter can be either a URL (see the section GIT URLS below) or the name of a remote (see the section REMOTES below).
A name referring to a list of repositories as the value of remotes.<group> in the configuration file. (See git-config(1)).
The format of a <refspec> parameter is an optional plus +, followed by the source ref <src>, followed by a colon :, followed by the destination ref <dst>.
The remote ref that matches <src> is fetched, and if <dst> is not empty string, the local ref that matches it is fast-forwarded using <src>. If the optional plus + is used, the local ref is updated even if it does not result in a fast-forward update.
|If the remote branch from which you want to pull is modified in non-linear ways such as being rewound and rebased frequently, then a pull will attempt a merge with an older version of itself, likely conflict, and fail. It is under these conditions that you would want to use the + sign to indicate non-fast-forward updates will be needed. There is currently no easy way to determine or declare that a branch will be made available in a repository with this beha|
|You never do your own development on branches that appear on the right hand side of a <refspec> colon on Pull: lines; they are to be updated by git fetch. If you intend to do development derived from a remote branch B, have a Pull: line to track it (i.e. Pull: B:remote-B), and have a separate branch my-B to do your development on top of it. The latter is created by git branch my-B remote-B (or its equivalent git checkout -b my-B remote-B). Run git fetch to keep track of the progress of the remote side, and when you see something new on the remote branch, merge it into your development branch with git pull . remote-B, while you are on my-B branch.|
|There is a difference between listing multiple <refspec> directly on git pull command line and having multiple Pull: <refspec> lines for a <repository> and running git pull command without any explicit <refspec> parameters.< refspec> listed explicitly on the command line are always merged into the current branch after fetching. In other words, if you list more than on|
Some short-cut notations are also supported.
tag <tag> means the same as refs/tags/<tag>:refs/tags/<tag>; it requests fetching everything up to the given tag.
A parameter <ref> without a colon fetches that ref into FETCH_HEAD, and updates the remote-tracking branches (if any).
$ git fetch origin +pu:pu maint:tmp