fetch-options.txt: prevent a wildcard refspec from getting misformatted
authorJunio C Hamano <gitster@pobox.com>
Fri, 7 Jun 2013 15:09:51 +0000 (08:09 -0700)
committerJunio C Hamano <gitster@pobox.com>
Fri, 7 Jun 2013 15:22:37 +0000 (08:22 -0700)
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>
Documentation/fetch-options.txt
index 6e98bdf1490a0a5718dd14a4c2d8b2baaee7383e..c87bf39cd0774784bb48b911e72fe9bc74b83f00 100644 (file)
@@ -57,7 +57,7 @@ endif::git-pull[]
 ifndef::git-pull[]
 -t::
 --tags::
-       This is a short-hand for giving "refs/tags/*:refs/tags/*"
+       This is a short-hand for giving `refs/tags/*:refs/tags/*`
        refspec from the command line, to ask all tags to be fetched
        and stored locally.  Because this acts as an explicit
        refspec, the default refspecs (configured with the