From: Junio C Hamano Date: Tue, 17 Oct 2017 02:31:06 +0000 (+0900) Subject: fetch doc: src side of refspec could be full SHA-1 X-Git-Tag: v2.14.3~2^2 X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/83558a412afa21e5eef1d97705204b8fb2c7a6f2?ds=inline;hp=--cc 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 Reviewed-by: Jonathan Nieder Signed-off-by: Junio C Hamano --- 83558a412afa21e5eef1d97705204b8fb2c7a6f2 diff --git a/Documentation/pull-fetch-param.txt b/Documentation/pull-fetch-param.txt index 1ebbf1d738..c579793af5 100644 --- a/Documentation/pull-fetch-param.txt +++ b/Documentation/pull-fetch-param.txt @@ -23,9 +23,11 @@ ifdef::git-pull[] endif::git-pull[] + The format of a parameter is an optional plus -`+`, followed by the source ref , followed +`+`, followed by the source , followed by a colon `:`, followed by the destination ref . -The colon can be omitted when is empty. +The colon can be omitted when is empty. is +typically a ref, but it can also be a fully spelled hex object +name. + `tag ` means the same as `refs/tags/:refs/tags/`; it requests fetching everything up to the given tag.