X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=Documentation%2Fgit-remote.txt;h=a9fb6a9a5ef3cfeffa37578b4d703ca75c73f306;hb=8391c60b6e08604e7023a8fff74350d6b35974af;hp=5b93a8c8be3299150a9f1045c1953fb914e01a33;hpb=38ebbacd93eb547b3608b64a2efc60fd79e1ea85;p=git.git diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt index 5b93a8c8b..886bc03c4 100644 --- a/Documentation/git-remote.txt +++ b/Documentation/git-remote.txt @@ -10,37 +10,88 @@ SYNOPSIS -------- [verse] 'git-remote' -'git-remote' add +'git-remote' add [-t ] [-m ] [-f] 'git-remote' show +'git-remote' prune +'git-remote' update [group] DESCRIPTION ----------- Manage the set of repositories ("remotes") whose branches you track. -With no arguments, shows a list of existing remotes. -In the second form, adds a remote named for the repository at +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 /. - -In the third form, gives some information about the remote . ++ +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. + +'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-repo-config[1]). +gitlink:git-config[1]). Examples -------- -Add a new remote, fetch, and check out a branch from it: - +* 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 add linux-nfs git://linux-nfs.org/pub/linux/nfs-2.6.git $ git remote linux-nfs origin @@ -54,11 +105,22 @@ $ 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-repo-config[1] +gitlink:git-config[1] Author ------ @@ -73,4 +135,3 @@ Documentation by J. Bruce Fields and the git-list . GIT --- Part of the gitlink:git[7] suite -