summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2017-10-19 14:45:44 +0900
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-10-19 14:45:45 +0900
commit39a2aeacc5c606b6b9a4c5b8397b02c35c38ae5f (patch)
tree47b1fda2db24f9ae83b56aea093ece3a1ece7a0c
parentMerge branch 'wk/merge-options-gpg-sign-doc' (diff)
parentfetch doc: src side of refspec could be full SHA-1 (diff)
downloadtgif-39a2aeacc5c606b6b9a4c5b8397b02c35c38ae5f.tar.xz
Merge branch 'jc/fetch-refspec-doc-update'
"git fetch <there> <src>:<dst>" allows an object name on the <src> side when the other side accepts such a request since Git v2.5, but the documentation was left stale. * jc/fetch-refspec-doc-update: fetch doc: src side of refspec could be full SHA-1
-rw-r--r--Documentation/pull-fetch-param.txt6
1 files changed, 4 insertions, 2 deletions
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 <refspec> parameter is an optional plus
-`+`, followed by the source ref <src>, followed
+`+`, followed by the source <src>, followed
by a colon `:`, followed by the destination ref <dst>.
-The colon can be omitted when <dst> is empty.
+The colon can be omitted when <dst> is empty. <src> is
+typically a ref, but it can also be a fully spelled hex object
+name.
+
`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`;
it requests fetching everything up to the given tag.