Documentation: clarify fetch parameter descriptions.

bfields · Junio C Hamano · commit c2bc6e404d75 · 2006-01-12T22:03:11.000-08:00
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
diff --git 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

Original file line number	Diff line number	Diff line change
`@@ -134,9 +134,9 @@ is often useful.`
`134`	`134`	`+`
`135`	`135`	`Some short-cut notations are also supported.`
`136`	`136`	`+`
`137`		-* For backward compatibility, `tag` is almost ignored;
`138`		`- it just makes the following parameter <tag> to mean a`
`139`		- refspec `refs/tags/<tag>:refs/tags/<tag>`.
	`137`	+* `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`;
	`138`	`+ used with pull or fetch, it requests fetching everything up to`
	`139`	`+ the given tag.`
`140`	`140`	`* A parameter <ref> without a colon is equivalent to`
`141`	`141`	<ref>: when pulling/fetching, and <ref>`:`<ref> when
`142`	`142`	`pushing. That is, do not store it locally if`