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

Re: [PATCH] docs: stop using asciidoc no-inline-literal

From
Jeff King <peff@peff.net>
Date
Apr 26, 2012, 09:13 UTC
Message-ID
<20120426091343.GA16663@sigill.intra.peff.net>
In-Reply-To
<vpqehra97wo.fsf@bauges.imag.fr>
On Thu, Apr 26, 2012 at 11:09:11AM +0200, Matthieu Moy wrote:
Show 7 quoted lines
> Jeff King <peff@peff.net> writes:
> 
> > The patch is below. I'm slightly nervous because it means topics in
> > flight will need to have their documentation tweaked, too.
> 
> ... or, at worse, they will be broken for a while, and we can grep again
> the tip of pu after a few weeks to fix them.

Yes. Though having just done that grep, it is quite tedious. You will get many false positives in the existing documentation that do not need changed (e.g., stash@{0}, or a literal backslash that is meant to be in the output). So I think it will be simpler to just diff Documentation/ for the new topics and scan them manually (or grep the diff output).

> Plus, the possible breakage due to your patch are compensated by the
> existing breakage you fixed ;-). So, I'd say this is a valid concern,
> but the benefit seem clearly greater than the drawbacks.
Yeah, that was my conclusion, too.
-Peff
Previous: Matthieu MoyNext: Thomas Rast
Message 4 of 8 in “docs: stop using asciidoc no-inline-literal”
  1. docs: stop using asciidoc no-inline-literalJeff King, Apr 26, 2012
  2. Jeff KingApr 26, 2012
  3. Matthieu MoyApr 26, 2012
  4. Jeff KingApr 26, 2012
  5. Thomas RastApr 26, 2012
  6. Thomas RastApr 26, 2012
  7. Jeff KingApr 26, 2012
  8. Thomas RastApr 26, 2012

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.