fetch doc: src side of refspec could be full SHA-1
Since a9d34933 ("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 <gitster@pobox.com> Reviewed-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Oct 17, 2017 at 11:31 UTC
83558a412afa21e5eef1d97705204b8fb2c7a6f2
1 file changed
+4
-2
Documentation/pull-fetch-param.txt
+4
-2
@@ -23,9 +23,11 @@ ifdef::git-pull[]
23
endif::git-pull[]
24
+
25
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
27
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
29
+typically a ref, but it can also be a fully spelled hex object
30
+name.
31
+
32
`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`;
33
it requests fetching everything up to the given tag.