1git-fetch(1) 2============ 3 4NAME 5---- 6git-fetch - Download objects and refs from another repository 7 8 9SYNOPSIS 10-------- 11[verse] 12'git fetch' [<options>] [<repository> [<refspec>...]] 13'git fetch' [<options>] <group> 14'git fetch' --multiple [<options>] [(<repository> | <group>)...] 15'git fetch' --all [<options>] 16 17 18DESCRIPTION 19----------- 20Fetches named heads or tags from one or more other repositories, 21along with the objects necessary to complete them. 22 23The ref names and their object names of fetched refs are stored 24in `.git/FETCH_HEAD`. This information is left for a later merge 25operation done by 'git merge'. 26 27When <refspec> stores the fetched result in remote-tracking branches, 28the tags that point at these branches are automatically 29followed. This is done by first fetching from the remote using 30the given <refspec>s, and if the repository has objects that are 31pointed by remote tags that it does not yet have, then fetch 32those missing tags. If the other end has tags that point at 33branches you are not interested in, you will not get them. 34 35'git fetch' can fetch from either a single named repository, 36or from several repositories at once if <group> is given and 37there is a remotes.<group> entry in the configuration file. 38(See linkgit:git-config[1]). 39 40OPTIONS 41------- 42include::fetch-options.txt[] 43 44include::pull-fetch-param.txt[] 45 46include::urls-remotes.txt[] 47 48 49EXAMPLES 50-------- 51 52* Update the remote-tracking branches: 53+ 54------------------------------------------------ 55$ git fetch origin 56------------------------------------------------ 57+ 58The above command copies all branches from the remote refs/heads/ 59namespace and stores them to the local refs/remotes/origin/ namespace, 60unless the branch.<name>.fetch option is used to specify a non-default 61refspec. 62 63* Using refspecs explicitly: 64+ 65------------------------------------------------ 66$ git fetch origin +pu:pu maint:tmp 67------------------------------------------------ 68+ 69This updates (or creates, as necessary) branches `pu` and `tmp` in 70the local repository by fetching from the branches (respectively) 71`pu` and `maint` from the remote repository. 72+ 73The `pu` branch will be updated even if it is does not fast-forward, 74because it is prefixed with a plus sign; `tmp` will not be. 75 76 77BUGS 78---- 79Using --recurse-submodules can only fetch new commits in already checked 80out submodules right now. When e.g. upstream added a new submodule in the 81just fetched commits of the superproject the submodule itself can not be 82fetched, making it impossible to check out that submodule later without 83having to do a fetch again. This is expected to be fixed in a future Git 84version. 85 86SEE ALSO 87-------- 88linkgit:git-pull[1] 89 90GIT 91--- 92Part of the linkgit:git[1] suite