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

Re: [PATCH 3/3] doc: git-config: escape erroneous adoc markup

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 10, 2026, 19:50 UTC
Message-ID
<xmqqecieuqdm.fsf@gitster.g>
In-Reply-To
<20260610185148.23920-4-taahol@utu.fi>
Tuomas Ahola <taahol@utu.fi> writes:
Show 12 quoted lines
> Paired octothorpes are used in AsciiDoc to mark highlighted text,
> <mark> being the equivalent HTML tag.  To use the symbol as a literal
> character, it can be escaped with a backslash.
>
> Do so in git-config.adoc.
>
> While at it, tweak the text slightly to make it scan better.
>
> Signed-off-by: Tuomas Ahola <taahol@utu.fi>
> ---
>  Documentation/git-config.adoc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
Thanks.  

What we see in https://git-scm.com/docs/git-config#Documentation/git-config.txt---commentmessage is rather embarrasing. This would be a vast improvement ;-)

Show 17 quoted lines
> diff --git a/Documentation/git-config.adoc b/Documentation/git-config.adoc
> index 8439ce97df..708e88cdeb 100644
> --- a/Documentation/git-config.adoc
> +++ b/Documentation/git-config.adoc
> @@ -119,10 +119,10 @@ OPTIONS
>  	Append a comment at the end of new or modified lines.
>  +
>  If _<message>_ begins with one or more whitespaces followed
> -by "#", it is used as-is.  If it begins with "#", a space is
> +by "\#", it is used as-is.  If it begins with "#", a space is
>  prepended before it is used.  Otherwise, a string " # " (a
>  space followed by a hash followed by a space) is prepended
> -to it.  And the resulting string is placed immediately after
> +to it.  The resulting string is placed immediately after
>  the value defined for the variable.  The _<message>_ must
>  not contain linefeed characters (no multi-line comments are
>  permitted).
Previous: Tuomas AholaNext: Junio C Hamano
Message 5 of 30 in “doc: config/sideband: fix typo in adoc markup”
  1. 2/3 doc: config/sideband: fix typo in adoc markupTuomas Ahola, Jun 10, 2026
  2. 3/3 doc: git-config: escape erroneous adoc markupTuomas Ahola, Jun 10, 2026
  3. 0/3 doc: config: fix AsciiDoc glitchesTuomas Ahola, Jun 10, 2026
  4. 1/3 doc: config: terminate runaway listsTuomas Ahola, Jun 10, 2026
  5. Junio C HamanoJun 10, 2026
  6. Junio C HamanoJun 10, 2026
  7. Kristoffer HaugsbakkJun 10, 2026
  8. 1/3 doc: config: terminate runaway listsTuomas Ahola, Jun 10, 2026
  9. 2/3 doc: config/sideband: fix description list delimiterTuomas Ahola, Jun 10, 2026
  10. 3/3 doc: git-config: escape erroneous highlight markupTuomas Ahola, Jun 10, 2026
  11. 0/3 doc: config: fix AsciiDoc glitchesTuomas Ahola, Jun 10, 2026
  12. Jeff KingJun 11, 2026
  13. Jeff KingJun 11, 2026
  14. Jeff KingJun 11, 2026
  15. Jeff KingJun 11, 2026
  16. Tuomas AholaJun 11, 2026
  17. Jeff KingJun 11, 2026
  18. Tuomas AholaJun 11, 2026
  19. 3/3 doc: git-config: escape erroneous highlight markupTuomas Ahola, Jun 11, 2026
  20. 1/3 doc: config: terminate runaway listsTuomas Ahola, Jun 11, 2026
  21. 0/3 doc: config: fix AsciiDoc glitchesTuomas Ahola, Jun 11, 2026
  22. 2/3 doc: config/sideband: fix description list delimiterTuomas Ahola, Jun 11, 2026
  23. Junio C HamanoJun 11, 2026
  24. Jean-Noël AVILAJun 11, 2026
  25. Jeff KingJun 12, 2026
  26. Jeff KingJun 12, 2026
  27. Jeff KingJun 12, 2026
  28. Junio C HamanoJun 12, 2026
  29. Junio C HamanoJun 12, 2026
  30. Junio C HamanoJun 12, 2026

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.