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

Re: how to patch git documentation

From
NKNeal Kreitzinger <nkreitzinger@gmail.com>
Date
Mar 9, 2012, 23:11 UTC
Message-ID
<4F5A8E0C.20404@gmail.com>
In-Reply-To
<7v1up2bikm.fsf@alter.siamese.dyndns.org>
On 3/8/2012 8:43 PM, Junio C Hamano wrote:
Show 6 quoted lines
> Neal Kreitzinger<nkreitzinger@gmail.com>  writes:
>
>> What language are the git documentation *.txt files written in?
> Mixture of Pidgin English and a bit of AsciiDoc ;-).
>
>

Does someone have documentation on how to test the AsciiDoc changes of their Documentation/ patches? This tester I found doesn't work right because it not only shows my asciidoc changes misformatted in html, but it also shows the original working asciidoc code from git.git as being misformatted in html : http://andrewk.webfactional.com/asciidoc.php

v/r, neal

Previous: Junio C Hamano
Message 5 of 5 in “how to patch git documentation”
  1. Neal KreitzingerMar 9, 2012
  2. Junio C HamanoMar 9, 2012
  3. Neal KreitzingerMar 9, 2012
  4. Junio C HamanoMar 9, 2012
  5. Neal KreitzingerMar 9, 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.