unsupported /ˆ¿Å ƒh¹¾Ã/unsupported 1ˆ¿Å 0¾Ã 3ˆ¿Å 0¾Ã 5ˆ¿Å 0¾Ã 7ˆ¿Å 0¾Ã 9ˆ¿Å 0¾Ã ;ˆ¿Å 0¾Ã+=ˆl–Ðz¾”ËmJeAàq¶ÔÅ£Æ ƒqöÙ_‡I|¥ŠèªÀÅ)=git-remote(1) ============ NAME ---- git-remote - manage set of tracked repositories SYNOPSIS -------- [verse] 'git remote' [-v | --verbose] 'git remote add' [-t ] [-m ] [-f] [--[no-]tags] [--mirror=] 'git remote rename' 'git remote remove' 'git remote set-head' (-a | -d | ) 'git remote set-branches' [--add] ... 'git remote set-url' [--push] [] 'git remote set-url --add' [--push] 'git remote set-url --delete' [--push] 'git remote' [-v | --verbose] 'show' [-n] ... 'git remote prune' [-n | --dry-run] ... 'git remote' [-v | --verbose] 'update' [-p | --prune] [( | )...] DESCRIPTION ----------- Manage the set of repositories ("remotes") whose branches you track. OPTIONS ------- -v:: --verbose:: Be a little more verbose and show remote url after name. NOTE: This must be placed between `remote` and `subcommand`. 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 `--tags` option, `git fetch ` imports every tag from the remote repository. + With `--no-tags` option, `git fetch ` does not import tags from the remote repository. + With `-t ` option, instead of the default glob refspec for the remote to track all branches under the `refs/remotes//` namespace, 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, a symbolic-ref `refs/remotes//HEAD` is set up to point at remote's `` branch. See also the set-head command. + When a fetch mirror is created with `--mirror=fetch`, the refs will not be stored in the 'refs/remotes/' namespace, but rather everything in 'refs/' on the remote will be directly mirrored into 'refs/' in the local repository. This option only makes sense in bare repositories, because a fetch would overwrite any local commits. + When a push mirror is created with `--mirror=push`, then `git push` will always behave as if `--mirror` was passed. 'rename':: Rename the remote named to . All remote-tracking branches and configuration settings for the remote are updated. + In case and are the same, and is a file under `$GIT_DIR/remotes` or `$GIT_DIR/branches`, the remote is converted to the configuration file format. 'remove':: 'rm':: Remove the remote named . All remote-tracking branches and configuration settings for the remote are removed. 'set-head':: Sets or deletes the default branch (i.e. the target of the symbolic-ref `refs/remotes//HEAD`) for the named remote. Having a default branch for a remote is not required, but allows the name of the remote to be specified in lieu of a specific branch. For example, if the default branch for `origin` is set to `master`, then `origin` may be specified wherever you would normally specify `origin/master`. + With `-d`, the symbolic ref `refs/remotes//HEAD` is deleted. + With `-a`, the remote is queried to determine its `HEAD`, then the symbolic-ref `refs/remotes//HEAD` is set to the same branch. e.g., if the remote `HEAD` is pointed at `next`, "`git remote set-head origin -a`" will set the symbolic-ref `refs/remotes/origin/HEAD` to `refs/remotes/origin/next`. This will only work if `refs/remotes/origin/next` already exists; if not it must be fetched first. + Use `` to set the symbolic-ref `