Skip to content

Commit 8e4414e

Browse files
jrngitster
authored andcommitted
Documentation: do not misinterpret refspecs as bold text
In v1.7.3.3~2 (Documentation: do not misinterpret pull refspec as bold text, 2010-12-03) many uses of asterisks in expressions like "refs/heads/*:refs/svn/origin/branches/*" were escaped as {asterisk} to avoid being treated as delimiters for bold text, but these two were missed. Signed-off-by: Jonathan Nieder <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 5b42477 commit 8e4414e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Documentation/git-remote-helpers.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -181,11 +181,11 @@ CAPABILITIES
181181
When using the import command, expect the source ref to have
182182
been written to the destination ref. The earliest applicable
183183
refspec takes precedence. For example
184-
"refs/heads/*:refs/svn/origin/branches/*" means that, after an
185-
"import refs/heads/name", the script has written to
184+
"refs/heads/{asterisk}:refs/svn/origin/branches/{asterisk}" means
185+
that, after an "import refs/heads/name", the script has written to
186186
refs/svn/origin/branches/name. If this capability is used at
187187
all, it must cover all refs reported by the list command; if
188-
it is not used, it is effectively "*:*"
188+
it is not used, it is effectively "{asterisk}:{asterisk}"
189189

190190
REF LIST ATTRIBUTES
191191
-------------------

0 commit comments

Comments
 (0)