undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

git-remote.txt: fix wrong remote refspec

Browse Source 
$GIT_DIR/remotes/<name>/<branch> should be
$GIT_DIR/refs/remotes/<name>/<branch>.

Signed-off-by: Namhyung Kim <namhyung@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Namhyung Kim 2011-06-23 17:12:04 +09:00 committed by Junio C Hamano
parent 4f8303905e
commit eb637e1382
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/git-remote.txt
View File

@ -60,11 +60,11 @@ the remote repository.
+ +
With `-t <branch>` option, instead of the default glob With `-t <branch>` option, instead of the default glob
refspec for the remote to track all branches under refspec for the remote to track all branches under
`$GIT_DIR/remotes/<name>/`, a refspec to track only `<branch>` `$GIT_DIR/refs/remotes/<name>/`, a refspec to track only `<branch>`
is created. You can give more than one `-t <branch>` to track is created. You can give more than one `-t <branch>` to track
multiple branches without grabbing all branches. multiple branches without grabbing all branches.
+ +
With `-m <master>` option, `$GIT_DIR/remotes/<name>/HEAD` is set With `-m <master>` option, `$GIT_DIR/refs/remotes/<name>/HEAD` is set
up to point at remote's `<master>` branch. See also the set-head command. up to point at remote's `<master>` branch. See also the set-head command.
+ +
When a fetch mirror is created with `\--mirror=fetch`, the refs will not When a fetch mirror is created with `\--mirror=fetch`, the refs will not
@ -92,23 +92,23 @@ configuration settings for the remote are removed.
'set-head':: 'set-head'::
Sets or deletes the default branch (`$GIT_DIR/remotes/<name>/HEAD`) for Sets or deletes the default branch (`$GIT_DIR/refs/remotes/<name>/HEAD`) for
the named remote. Having a default branch for a remote is not required, 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 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 branch. For example, if the default branch for `origin` is set to
`master`, then `origin` may be specified wherever you would normally `master`, then `origin` may be specified wherever you would normally
specify `origin/master`. specify `origin/master`.
+ +
With `-d`, `$GIT_DIR/remotes/<name>/HEAD` is deleted. With `-d`, `$GIT_DIR/refs/remotes/<name>/HEAD` is deleted.
+ +
With `-a`, the remote is queried to determine its `HEAD`, then With `-a`, the remote is queried to determine its `HEAD`, then
`$GIT_DIR/remotes/<name>/HEAD` is set to the same branch. e.g., if the remote `$GIT_DIR/refs/remotes/<name>/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 `HEAD` is pointed at `next`, "`git remote set-head origin -a`" will set
`$GIT_DIR/refs/remotes/origin/HEAD` to `refs/remotes/origin/next`. This will `$GIT_DIR/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 only work if `refs/remotes/origin/next` already exists; if not it must be
fetched first. fetched first.
+ +
Use `<branch>` to set `$GIT_DIR/remotes/<name>/HEAD` explicitly. e.g., "git Use `<branch>` to set `$GIT_DIR/refs/remotes/<name>/HEAD` explicitly. e.g., "git
remote set-head origin master" will set `$GIT_DIR/refs/remotes/origin/HEAD` to remote set-head origin master" will set `$GIT_DIR/refs/remotes/origin/HEAD` to
`refs/remotes/origin/master`. This will only work if `refs/remotes/origin/master`. This will only work if
`refs/remotes/origin/master` already exists; if not it must be fetched first. `refs/remotes/origin/master` already exists; if not it must be fetched first.