fetch-options.txt: prevent a wildcard refspec from getting misformatted
When explaining the "--tags" option as an equivalent to giving an explicit "refs/tags/*:refs/tags/*" refspec, the two asterisks were misinterpreted by AsciiDoc as a request to typeset the string segment between them in bold. We could fix it in two ways. We can replace them with {asterisk}s while keeping the string as body text, or we can mark it as a literal string with backquotes around it. Let's do the latter, as it is teaching the user an "exactly as typed" alternative. Noticed-by: Ramkumar Ramachandra <artagnon@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Jun 7, 2013 at 08:09 UTC
9eb4754d7682aa10c6dcbcc503a50a716d9cfc8a
1 file changed
+1
-1
Documentation/fetch-options.txt
+1
-1
@@ -57,7 +57,7 @@ endif::git-pull[]
57
ifndef::git-pull[]
58
-t::
59
--tags::
60
- This is a short-hand for giving "refs/tags/*:refs/tags/*"
60
+ This is a short-hand for giving `refs/tags/*:refs/tags/*`
61
refspec from the command line, to ask all tags to be fetched
62
and stored locally. Because this acts as an explicit
63
refspec, the default refspecs (configured with the