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

Documentation: do not misinterpret refspecs as bold text

Browse Source 
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 <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Jonathan Nieder 2011-05-30 10:52:56 -05:00 committed by Junio C Hamano
parent 5b42477b59
commit 8e4414edde
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/git-remote-helpers.txt
View File

@ -181,11 +181,11 @@ CAPABILITIES
When using the import command, expect the source ref to have When using the import command, expect the source ref to have
been written to the destination ref. The earliest applicable been written to the destination ref. The earliest applicable
refspec takes precedence. For example refspec takes precedence. For example
"refs/heads/*:refs/svn/origin/branches/*" means that, after an "refs/heads/{asterisk}:refs/svn/origin/branches/{asterisk}" means
"import refs/heads/name", the script has written to that, after an "import refs/heads/name", the script has written to
refs/svn/origin/branches/name. If this capability is used at refs/svn/origin/branches/name. If this capability is used at
all, it must cover all refs reported by the list command; if all, it must cover all refs reported by the list command; if
it is not used, it is effectively "*:*" it is not used, it is effectively "{asterisk}:{asterisk}"
REF LIST ATTRIBUTES REF LIST ATTRIBUTES
------------------- -------------------