aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@fieldses.org>2006-01-12 22:08:37 -0500
committerJunio C Hamano <junkio@cox.net>2006-01-12 22:03:11 -0800
commitc2bc6e404d75a3a68da5eefa47fa867569bc3339 (patch)
treedad40a826af0a66e750524ed20f399706da3842d
parent87758f975b04233ba058750f7ea8ce63bb67297f (diff)
downloadgit-c2bc6e404d75a3a68da5eefa47fa867569bc3339.tar.gz
git-c2bc6e404d75a3a68da5eefa47fa867569bc3339.tar.xz
Documentation: clarify fetch parameter descriptions.
Signed-off-by: Junio C Hamano <junkio@cox.net>
-rw-r--r--Documentation/pull-fetch-param.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/pull-fetch-param.txt b/Documentation/pull-fetch-param.txt
index b5b979242..4524fee6f 100644
--- a/Documentation/pull-fetch-param.txt
+++ b/Documentation/pull-fetch-param.txt
@@ -134,9 +134,9 @@ is often useful.
+
Some short-cut notations are also supported.
+
-* For backward compatibility, `tag` is almost ignored;
- it just makes the following parameter <tag> to mean a
- refspec `refs/tags/<tag>:refs/tags/<tag>`.
+* `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`;
+ used with pull or fetch, it requests fetching everything up to
+ the given tag.
* A parameter <ref> without a colon is equivalent to
<ref>: when pulling/fetching, and <ref>`:`<ref> when
pushing. That is, do not store it locally if