git-remote(1) ============ NAME ---- git-remote - manage set of tracked repositories SYNOPSIS -------- [verse] 'git-remote' 'git-remote' add [-t ] [-m ] [-f] [--mirror] 'git-remote' rm 'git-remote' show 'git-remote' prune 'git-remote' update [group] DESCRIPTION ----------- Manage the set of repositories ("remotes") whose branches you track. COMMANDS -------- With no arguments, shows a list of existing remotes. Several subcommands are available to perform operations on the remotes. 'add':: Adds a remote named for the repository at . The command `git fetch ` can then be used to create and update remote-tracking branches /. + With `-f` option, `git fetch ` is run immediately after the remote information is set up. + With `-t ` option, instead of the default glob refspec for the remote to track all branches under `$GIT_DIR/remotes//`, a refspec to track only `` is created. You can give more than one `-t ` to track multiple branches without grabbing all branches. + With `-m ` option, `$GIT_DIR/remotes//HEAD` is set up to point at remote's `` branch instead of whatever branch the `HEAD` at the remote repository actually points at. + In mirror mode, enabled with `--mirror`, the refs will not be stored in the 'refs/remotes/' namespace, but in 'refs/heads/'. This option only makes sense in bare repositories. 'rm':: Remove the remote named . All remote tracking branches and configuration settings for the remote are removed. 'show':: Gives some information about the remote . + With `-n` option, the remote heads are not queried first with `git ls-remote `; cached information is used instead. 'prune':: Deletes all stale tracking branches under . These stale branches have already been removed from the remote repository referenced by , but are still locally available in "remotes/". + With `-n` option, the remote heads are not confirmed first with `git ls-remote `; cached information is used instead. Use with caution. 'update':: Fetch updates for a named set of remotes in the repository as defined by remotes.. If a named group is not specified on the command line, the configuration parameter remotes.default will get used; if remotes.default is not defined, all remotes which do not have the configuration parameter remote..skipDefaultUpdate set to true will be updated. (See gitlink:git-config[1]). DISCUSSION ---------- The remote configuration is achieved using the `remote.origin.url` and `remote.origin.fetch` configuration variables. (See gitlink:git-config[1]). Examples -------- * Add a new remote, fetch, and check out a branch from it + ------------ $ git remote origin $ git branch -r origin/master $ git remote add linux-nfs git://linux-nfs.org/pub/nfs-2.6.git $ git remote linux-nfs origin $ git fetch * refs/remotes/linux-nfs/master: storing branch 'master' ... commit: bf81b46 $ git branch -r origin/master linux-nfs/master $ git checkout -b nfs linux-nfs/master ... ------------ * Imitate 'git clone' but track only selected branches + ------------ $ mkdir project.git $ cd project.git $ git init $ git remote add -f -t master -m master origin git://example.com/git.git/ $ git merge origin ------------ See Also -------- gitlink:git-fetch[1] gitlink:git-branch[1] gitlink:git-config[1] Author ------ Written by Junio Hamano Documentation -------------- Documentation by J. Bruce Fields and the git-list . GIT --- Part of the gitlink:git[7] suite