Re: asciidoc problem, and a possible fix

hachi [off-list ref] 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.

* 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.