Skip to content

Commit f62ecee

Browse files
committed
fetch doc: src side of refspec could be full SHA-1
Since a9d3493 ("Merge branch 'fm/fetch-raw-sha1'", 2015-06-01) we allow to fetch by an object name when the other side accepts such a request, but we never updated the documentation to match. Signed-off-by: Junio C Hamano <[email protected]>
1 parent a9d3493 commit f62ecee

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

Documentation/pull-fetch-param.txt

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,11 @@ ifdef::git-pull[]
2323
endif::git-pull[]
2424
+
2525
The format of a <refspec> parameter is an optional plus
26-
`+`, followed by the source ref <src>, followed
26+
`+`, followed by the source <src>, followed
2727
by a colon `:`, followed by the destination ref <dst>.
28-
The colon can be omitted when <dst> is empty.
28+
The colon can be omitted when <dst> is empty. <src> is most
29+
typically a ref, but it can also be an fully spelled hex object
30+
name.
2931
+
3032
`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`;
3133
it requests fetching everything up to the given tag.

0 commit comments

Comments
 (0)