From: Junio C Hamano Date: Mon, 26 Feb 2007 08:32:19 +0000 (-0800) Subject: Merge branch 'maint' X-Git-Tag: v1.5.1-rc1~129 X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/8807d321af394ffb2180d085669337bcd5018c50?ds=inline;hp=-c Merge branch 'maint' * maint: GIT 1.5.0.2 git-remote: support remotes with a dot in the name Documentation: describe "-f/-t/-m" options to "git-remote add" diff --cc: fix display of symlink conflicts during a merge. --- 8807d321af394ffb2180d085669337bcd5018c50 diff --combined Documentation/git-remote.txt index 250761f97e,a2ff8f098e..266faade31 --- a/Documentation/git-remote.txt +++ b/Documentation/git-remote.txt @@@ -13,7 -13,6 +13,7 @@@ SYNOPSI 'git-remote' add 'git-remote' show 'git-remote' prune +'git-remote' update [group] DESCRIPTION ----------- @@@ -32,6 -31,19 +32,19 @@@ subcommands are available to perform op 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 branche 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':: @@@ -41,17 -53,7 +54,17 @@@ Gives some information about the remot 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/". +referenced by , but are still locally available in +"remotes/". + +'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 the +configuration parameter remote..skipDefaultUpdate set to true will +be updated. (See gitlink:git-config[1]). DISCUSSION