git-remote.txt: fix wrong remote refspec
$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>
Namhyung Kim committed
Jun 23, 2011 at 17:12 UTC
eb637e138289dc5b96bea5b192cbaff93623d1dc
1 file changed
+6
-6
Documentation/git-remote.txt
+6
-6
@@ -60,11 +60,11 @@ the remote repository.
60
+
61
With `-t <branch>` option, instead of the default glob
62
refspec for the remote to track all branches under
63
-`$GIT_DIR/remotes/<name>/`, a refspec to track only `<branch>`
63
+`$GIT_DIR/refs/remotes/<name>/`, a refspec to track only `<branch>`
64
is created. You can give more than one `-t <branch>` to track
65
multiple branches without grabbing all branches.
66
+
67
-With `-m <master>` option, `$GIT_DIR/remotes/<name>/HEAD` is set
67
+With `-m <master>` option, `$GIT_DIR/refs/remotes/<name>/HEAD` is set
68
up to point at remote's `<master>` branch. See also the set-head command.
69
+
70
When a fetch mirror is created with `\--mirror=fetch`, the refs will not
@@ -92,23 +92,23 @@ configuration settings for the remote are removed.
92
93
'set-head'::
94
95
-Sets or deletes the default branch (`$GIT_DIR/remotes/<name>/HEAD`) for
95
+Sets or deletes the default branch (`$GIT_DIR/refs/remotes/<name>/HEAD`) for
96
the named remote. Having a default branch for a remote is not required,
97
but allows the name of the remote to be specified in lieu of a specific
98
branch. For example, if the default branch for `origin` is set to
99
`master`, then `origin` may be specified wherever you would normally
100
specify `origin/master`.
101
+
102
-With `-d`, `$GIT_DIR/remotes/<name>/HEAD` is deleted.
102
+With `-d`, `$GIT_DIR/refs/remotes/<name>/HEAD` is deleted.
103
+
104
With `-a`, the remote is queried to determine its `HEAD`, then
105
-`$GIT_DIR/remotes/<name>/HEAD` is set to the same branch. e.g., if the remote
105
+`$GIT_DIR/refs/remotes/<name>/HEAD` is set to the same branch. e.g., if the remote
106
`HEAD` is pointed at `next`, "`git remote set-head origin -a`" will set
107
`$GIT_DIR/refs/remotes/origin/HEAD` to `refs/remotes/origin/next`. This will
108
only work if `refs/remotes/origin/next` already exists; if not it must be
109
fetched first.
110
+
111
-Use `<branch>` to set `$GIT_DIR/remotes/<name>/HEAD` explicitly. e.g., "git
111
+Use `<branch>` to set `$GIT_DIR/refs/remotes/<name>/HEAD` explicitly. e.g., "git
112
remote set-head origin master" will set `$GIT_DIR/refs/remotes/origin/HEAD` to
113
`refs/remotes/origin/master`. This will only work if
114
`refs/remotes/origin/master` already exists; if not it must be fetched first.