summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2017-10-23 14:39:08 +0900
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-10-23 14:39:08 +0900
commit9fc7bc656858ef1b2d8f18856af59e23cda489d8 (patch)
tree53a5b3cd5e8de860d14d6bb17aa519da96b71914
parentMerge branch 'jk/write-in-full-fix' into maint (diff)
parentfetch doc: src side of refspec could be full SHA-1 (diff)
downloadtgif-9fc7bc656858ef1b2d8f18856af59e23cda489d8.tar.xz
Merge branch 'jc/fetch-refspec-doc-update' into maint
"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.