Documentation: clarify fetch parameter descriptions.
Signed-off-by: Junio C Hamano <junkio@cox.net>maint
parent
87758f975b
commit
c2bc6e404d
|
@ -134,9 +134,9 @@ is often useful.
|
||||||
+
|
+
|
||||||
Some short-cut notations are also supported.
|
Some short-cut notations are also supported.
|
||||||
+
|
+
|
||||||
* For backward compatibility, `tag` is almost ignored;
|
* `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`;
|
||||||
it just makes the following parameter <tag> to mean a
|
used with pull or fetch, it requests fetching everything up to
|
||||||
refspec `refs/tags/<tag>:refs/tags/<tag>`.
|
the given tag.
|
||||||
* A parameter <ref> without a colon is equivalent to
|
* A parameter <ref> without a colon is equivalent to
|
||||||
<ref>: when pulling/fetching, and <ref>`:`<ref> when
|
<ref>: when pulling/fetching, and <ref>`:`<ref> when
|
||||||
pushing. That is, do not store it locally if
|
pushing. That is, do not store it locally if
|
||||||
|
|
Loading…
Reference in New Issue