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

Re: [PATCH] Documentation: add a README file

From
Yann Droneaud <ydroneaud@opteya.com>
Date
Mar 21, 2013, 22:02 UTC
Message-ID
<1363903330.6289.59.camel@test.quest-ce.net>
In-Reply-To
<7v620ka1y8.fsf@alter.siamese.dyndns.org>
Hi,
Le jeudi 21 mars 2013 à 14:16 -0700, Junio C Hamano a écrit :
Show 16 quoted lines
> diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
> index b1bfff6..7e4d571 100644
> --- a/Documentation/CodingGuidelines
> +++ b/Documentation/CodingGuidelines
> @@ -237,6 +237,9 @@ For Python scripts:
>  
>  Writing Documentation:
>  
> + Most (if not all) of the documentation pages are written in AsciiDoc
> + and processed into HTML output and manpages.
> +
>   Every user-visible change should be reflected in the documentation.
>   The same general rule as for code applies -- imitate the existing
>   conventions.  A few commented examples follow to provide reference
> 
> 

Nice, I'm OK with this change. (But still thinking a README would be useful *too*).

Regards.
-- 
Yann Droneaud
OPTEYA
Previous: Junio C HamanoNext: Yann Droneaud
Message 6 of 8 in “Documentation: add a README file”
  1. Documentation: add a README fileYann Droneaud, Mar 21, 2013
  2. Junio C HamanoMar 21, 2013
  3. Yann DroneaudMar 21, 2013
  4. Junio C HamanoMar 21, 2013
  5. Junio C HamanoMar 21, 2013
  6. Yann DroneaudMar 21, 2013
  7. Yann DroneaudMar 21, 2013
  8. Jonathan NiederMar 21, 2013

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.