6 git-remote - manage set of tracked repositories
13 'git-remote' add <name> <url>
14 'git-remote' show <name>
15 'git-remote' prune <name>
21 Manage the set of repositories ("remotes") whose branches you track.
27 With no arguments, shows a list of existing remotes. Several
28 subcommands are available to perform operations on the remotes.
32 Adds a remote named <name> for the repository at
33 <url>. The command `git fetch <name>` can then be used to create and
34 update remote-tracking branches <name>/<branch>.
38 Gives some information about the remote <name>.
42 Deletes all stale tracking branches under <name>.
43 These stale branches have already been removed from the remote repository
44 referenced by <name>, but are still locally available in
49 Fetch updates for the remotes in the repository. By default all remotes
50 are updated, but this can be configured via the configuration parameter
51 'remote.fetch'. (See gitlink:git-config[1]).
57 The remote configuration is achieved using the `remote.origin.url` and
58 `remote.origin.fetch` configuration variables. (See
59 gitlink:git-config[1]).
64 Add a new remote, fetch, and check out a branch from it:
71 $ git remote add linux-nfs git://linux-nfs.org/pub/nfs-2.6.git
76 * refs/remotes/linux-nfs/master: storing branch 'master' ...
81 $ git checkout -b nfs linux-nfs/master
93 Written by Junio Hamano
98 Documentation by J. Bruce Fields and the git-list <git@vger.kernel.org>.
103 Part of the gitlink:git[7] suite