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

Re: [PATCH] doc: fix accidental literal blocks

From
Jeff King <peff@peff.net>
Date
Oct 10, 2025, 05:02 UTC
Message-ID
<20251010050207.GA1897715@coredump.intra.peff.net>
In-Reply-To
<7a955ecb1b5.1759923933.git.code@khaugsbakk.name>
On Wed, Oct 08, 2025 at 01:48:46PM +0200, kristofferhaugsbakk@fastmail.com wrote:
Show 9 quoted lines
> Make sure that normal paragraphs in most user-facing docs[1] don’t
> use literal blocks. This can easily happen if you try to maintain
> indentation in order to continue a block; that might work in
> e.g. Markdown variants, but not in AsciiDoc.
> 
> The fixes are straightforward, i.e. just deindent the block and maybe
> add line continuations. The only exception is git-sparse-checkout(1)
> where we also replace indentation used for *intended* literal blocks
> with `----`.

I gave a quick look over the results of doc-diff before and after, and all of the changes look good to me.

-Peff
Previous: kristofferhaugsbakk@fastmail.comNext: Kristoffer Haugsbakk
Message 2 of 4 in “doc: fix accidental literal blocks”
  1. doc: fix accidental literal blockskristofferhaugsbakk@fastmail.com, Oct 8, 2025
  2. Jeff KingOct 10, 2025
  3. Kristoffer HaugsbakkOct 10, 2025
  4. doc: fix accidental literal blockskristofferhaugsbakk@fastmail.com, Oct 10, 2025

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.