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

Re: [PATCH] Fix AsciiDoc errors in merge documentation

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 4, 2008, 23:19 UTC
Message-ID
<7vbpz31oup.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200809042348.48570.johan@herland.net>
Johan Herland <johan@herland.net> writes:
Show 19 quoted lines
> In the section on conflict markers, the "<<<<<<<" sequence is compiled by
> AsciiDoc into invalid XML. A way to resolve this is by inserting something
> between the last two characters in that sequence (i.e. between '<' and '"').
>
> This patch encloses the conflict markers in backticks, which renders them
> in a monospace font (in the HTML version; the manual page is unaffected),
> and with the pleasant side-effect that it also fixes the AsciiDoc compile
> problem.
>
> Signed-off-by: Johan Herland <johan@herland.net>
> ---
>
> On Thursday 04 September 2008, Gustaf Hendeby wrote:
>> Trying to compile the documentation from next has failed for me for a
>> while and now I got to the point where I tracked down the offending
>> commit: 70a3f89733a (git-merge documentation: describe how conflict is
>> presented).
>
> This fixes the problem for me.

Thanks. It's good to see issues with new changes are resolved while they are still in 'next'.

Have you tried this patch without double quotes around the teletype text, by the way?

Previous: Gustaf HendebyNext: Johan Herland
Message 4 of 5 in “[BUG] Problem compiling documentation”
  1. Gustaf HendebySep 4, 2008
  2. Fix AsciiDoc errors in merge documentationJohan Herland, Sep 4, 2008
  3. Gustaf HendebySep 4, 2008
  4. Junio C HamanoSep 4, 2008
  5. Johan HerlandSep 5, 2008

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.