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

Re: [PATCH v2 0/3] A few Asciidoctor-fixes

From
Jeff King <peff@peff.net>
Date
Dec 16, 2018, 16:19 UTC
Message-ID
<20181216161919.GB1511@sigill.intra.peff.net>
In-Reply-To
<cover.1544969984.git.martin.agren@gmail.com>
On Sun, Dec 16, 2018 at 03:28:56PM +0100, Martin Ågren wrote:
Show 6 quoted lines
> This series addresses a few instances where our documentation renders
> badly in Asciidoctor, compared to Asciidoc. The changes made are exactly
> the same as in v1 [1], but the first commit message is corrected, and
> the two patches 2/4 and 3/4 are now just a single patch 2/3.
> 
> Thanks Peff for your comments on v1.

Thanks, this all looks quite sensible to me (I didn't hack up doc-diff as you did, but I did eyeball the before/after html from asciidoctor).

-Peff
Previous: Martin ÅgrenNext: Jeff King
Message 15 of 18 in “A few Asciidoctor-fixes”
  1. 0/4 A few Asciidoctor-fixesMartin Ågren, Dec 15, 2018
  2. 1/4 git-column.txt: fix section headerMartin Ågren, Dec 15, 2018
  3. Jeff KingDec 16, 2018
  4. Martin ÅgrenDec 16, 2018
  5. 2/4 git-init.txt: do not nest open blocksMartin Ågren, Dec 15, 2018
  6. Jeff KingDec 16, 2018
  7. 3/4 rev-list-options.txt: do not nest open blocksMartin Ågren, Dec 15, 2018
  8. Jeff KingDec 16, 2018
  9. 4/4 git-status.txt: render tables correctly under AsciidoctorMartin Ågren, Dec 15, 2018
  10. Jeff KingDec 16, 2018
  11. 0/3 A few Asciidoctor-fixesMartin Ågren, Dec 16, 2018
  12. 1/3 git-column.txt: fix section headerMartin Ågren, Dec 16, 2018
  13. 2/3 Documentation: do not nest open blocksMartin Ågren, Dec 16, 2018
  14. 3/3 git-status.txt: render tables correctly under AsciidoctorMartin Ågren, Dec 16, 2018
  15. Jeff KingDec 16, 2018
  16. Jeff KingDec 16, 2018
  17. Martin ÅgrenDec 16, 2018
  18. Jeff KingDec 16, 2018

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.