undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fetch-options.txt: prevent a wildcard refspec from getting misformatted

Browse Source 
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>
This commit is contained in:
Junio C Hamano 2013-06-07 08:09:51 -07:00
parent 15999998fb
commit 9eb4754d76
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/fetch-options.txt
View File

@ -57,7 +57,7 @@ endif::git-pull[]
ifndef::git-pull[] ifndef::git-pull[]
-t:: -t::
--tags:: --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 refspec from the command line, to ask all tags to be fetched
and stored locally. Because this acts as an explicit and stored locally. Because this acts as an explicit
refspec, the default refspecs (configured with the refspec, the default refspecs (configured with the