git-fetch(1) ============ NAME ---- git-fetch - Download objects and refs from another repository SYNOPSIS -------- [verse] 'git fetch' [] [ [...]] 'git fetch' [] 'git fetch' --multiple [] [( | )...] 'git fetch' --all [] DESCRIPTION ----------- Fetches named heads or tags from one or more other repositories, along with the objects necessary to complete them. 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 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 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. 'git fetch' can fetch from either a single named repository, or from several repositories at once if is given and there is a remotes. entry in the configuration file. (See linkgit:git-config[1]). OPTIONS ------- include::fetch-options.txt[] include::pull-fetch-param.txt[] include::urls-remotes.txt[] EXAMPLES -------- * Update the remote-tracking branches: + ------------------------------------------------ $ git fetch origin ------------------------------------------------ + The above command copies all branches from the remote refs/heads/ namespace and stores them to the local refs/remotes/origin/ namespace, unless the branch..fetch option is used to specify a non-default refspec. * Using refspecs explicitly: + ------------------------------------------------ $ git fetch origin +pu:pu maint:tmp ------------------------------------------------ + This updates (or creates, as necessary) branches `pu` and `tmp` in the local repository by fetching from the branches (respectively) `pu` and `maint` from the remote repository. + The `pu` branch will be updated even if it is does not fast-forward, because it is prefixed with a plus sign; `tmp` will not be. BUGS ---- Using --recurse-submodules can only fetch new commits in already checked out submodules right now. When e.g. upstream added a new submodule in the just fetched commits of the superproject the submodule itself can not be fetched, making it impossible to check out that submodule later without having to do a fetch again. This is expected to be fixed in a future git version. SEE ALSO -------- linkgit:git-pull[1] GIT --- Part of the linkgit:git[1] suite