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

Re: asciidoc problem, and a possible fix

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 29, 2010, 06:38 UTC
Message-ID
<7vaatrbpjc.fsf@alter.siamese.dyndns.org>
In-Reply-To
<167EA641-2D5F-4553-909C-DF5D050CEDFB@kuiki.net>
hachi <hachi@kuiki.net> writes:
> The long version:
> ...
> End conclusion:

Thanks. The above analysis would be a good foundation for you to write a proper commit message when you submit a patch for application. Please see Documentation/SubmittingPatches.

Show 7 quoted lines
> * Option 1
>
> My patch is correct because nested inline passthrough doesn't do
> anything other than confuse the asciidoc parser. However, this means
> that prior to asciidoc 8.4.1 the inside of backtick strings are not
> inline passthrough. I have no idea if this is a bad thing, but it seems
> to not actually matter in my test using asciidoc 8.2.6.

I'd really want to avoid anything that does not work with AsciiDoc 8.2.5, as that is what is used to format the html/man branches at k.org.

Previous: hachi
Message 4 of 4 in “asciidoc problem, and a possible fix”
  1. hachiMar 24, 2010
  2. Junio C HamanoMar 25, 2010
  3. hachiMar 25, 2010
  4. Junio C HamanoMar 29, 2010

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.