6 git-remote - manage set of tracked repositories
13 'git-remote' add <name> <url>
14 'git-remote' show <name>
15 'git-remote' prune <name>
16 'git-remote' update [group]
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 a named set of remotes in the repository as defined by
50 remotes.<group>. If a named group is not specified on the command line,
51 the configuration parameter remotes.default will get used; if
52 remotes.default is not defined, all remotes which do not the
53 configuration parameter remote.<name>.skipDefaultUpdate set to true will
54 be updated. (See gitlink:git-config[1]).
60 The remote configuration is achieved using the `remote.origin.url` and
61 `remote.origin.fetch` configuration variables. (See
62 gitlink:git-config[1]).
67 Add a new remote, fetch, and check out a branch from it:
74 $ git remote add linux-nfs git://linux-nfs.org/pub/nfs-2.6.git
79 * refs/remotes/linux-nfs/master: storing branch 'master' ...
84 $ git checkout -b nfs linux-nfs/master
96 Written by Junio Hamano
101 Documentation by J. Bruce Fields and the git-list <git@vger.kernel.org>.
106 Part of the gitlink:git[7] suite