git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: pull-fetch-param.txt

From
SRStefan Richter <stefanr@s5r6.in-berlin.de>
Date
Oct 4, 2006, 17:15 UTC
Message-ID
<4523EC14.6070806@s5r6.in-berlin.de>
In-Reply-To
<4523E120.6050007@s5r6.in-berlin.de>
I wrote:
Show 20 quoted lines
> Junio C Hamano wrote:
>> Can you try reformatting the original
>>
>>> <refspec>::
>>> 	The canonical format of a <refspec> parameter is
>>> 	`+?<src>:<dst>`; that is, an optional plus `+`, followed
>>> 	by the source ref, followed by a colon `:`, followed by
>>> 	the destination ref.
>> to something like
>>
>>> <refspec>::
>>> 	The canonical format of a <refspec> parameter is
>>> 	`+?<src>:<dst>`; that is, an optional plus
>>> 	`+`, followed
>>> 	by the source ref, followed by a colon `:`, followed by
>>> 	the destination ref.
>> and verify that conjecture?
> 
> This hack does not help. The two `+` are still absent from the manpage
> (but as before, the `+` in the next paragraph is printed as desired).

After a few more experiments with different placements of backticks et cetera, I found only the following variants to work with asciidoc 8:

(as mentioned, not compatible to asciidoc 7):
	`$$+$$?<src>:<dst>`; that is, an optional plus `+`, followed
(as mentioned, compatible)
	`\+?<src>:<dst>`; that is, an optional plus `+`, followed
(also OK, and this is probably the only really correct syntax)
	`\+?<src>:<dst>`; that is, an optional plus `\+`, followed
(also OK but misses the monospace formatting on the plus or on the plus
and questionmark)
	\+`?<src>:<dst>`; that is, an optional plus `+`, followed
	\+?`<src>:<dst>`; that is, an optional plus `+`, followed
	\+?`<src>:<dst>`; that is, an optional plus \+, followed
	`\+?<src>:<dst>`; that is, an optional plus +, followed
Note,
	`+``?<src>:<dst>`; that is, an optional plus `+`, followed
does _not_ work. It stops on invalid syntax in the intermediary xml
file. Also
	+\+?<src>:<dst>+; that is, an optional plus `+`, followed
or
	`+`+?<src>:<dst>+; that is, an optional plus `+`, followed
do _not_ work. They don't print what we want to see.
-- 
Stefan Richter
-=====-=-==- =-=- --=--
http://arcgraph.de/sr/
Previous: Stefan RichterNext: Gerrit Pape
Message 14 of 23 in “escape tilde in Documentation/git-rev-parse.txt”
  1. escape tilde in Documentation/git-rev-parse.txtStefan Richter, Oct 2, 2006
  2. Junio C HamanoOct 3, 2006
  3. Stefan RichterOct 3, 2006
  4. Junio C HamanoOct 3, 2006
  5. pull-fetch-param.txt (was Re: [PATCH] escape tilde in Documentation/git-rev-parse.txt)Stefan Richter, Oct 3, 2006
  6. Junio C HamanoOct 3, 2006
  7. Stuart RackhamOct 3, 2006
  8. Junio C HamanoOct 4, 2006
  9. asciidoc 7--8 compatibility (was Re: pull-fetch-param.txt)Stefan Richter, Oct 4, 2006
  10. Stuart RackhamOct 4, 2006
  11. Stefan RichterOct 4, 2006
  12. Stuart RackhamOct 4, 2006
  13. Stefan RichterOct 4, 2006
  14. Stefan RichterOct 4, 2006
  15. Gerrit PapeJul 12, 2007
  16. Junio C HamanoJul 12, 2007
  17. Gerrit PapeJul 13, 2007
  18. Junio C HamanoJul 13, 2007
  19. Gerrit PapeJul 13, 2007
  20. Gerrit PapeJul 20, 2007
  21. Junio C HamanoJul 20, 2007
  22. Julian PhillipsJul 20, 2007
  23. Junio C HamanoJul 20, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.