Skip to content

Commit

Permalink
fetch-options.txt: prevent a wildcard refspec from getting misformatted
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
Junio C Hamano committed Jun 7, 2013
1 parent 1599999 commit 9eb4754
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Documentation/fetch-options.txt
Original file line number Diff line number Diff line change
@@ -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

0 comments on commit 9eb4754

Please sign in to comment.