All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann Droneaud <ydroneaud@opteya.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation: add a README file
Date: Thu, 21 Mar 2013 23:02:10 +0100	[thread overview]
Message-ID: <1363903330.6289.59.camel@test.quest-ce.net> (raw)
In-Reply-To: <7v620ka1y8.fsf@alter.siamese.dyndns.org>

Hi,

Le jeudi 21 mars 2013 à 14:16 -0700, Junio C Hamano a écrit :

> 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

  reply	other threads:[~2013-03-21 22:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 13:45 [PATCH] Documentation: add a README file Yann Droneaud
2013-03-21 15:31 ` Junio C Hamano
2013-03-21 15:49   ` Yann Droneaud
2013-03-21 17:39     ` Junio C Hamano
2013-03-21 21:16       ` Junio C Hamano
2013-03-21 22:02         ` Yann Droneaud [this message]
2013-03-21 21:59       ` Yann Droneaud
2013-03-21 22:09         ` Jonathan Nieder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1363903330.6289.59.camel@test.quest-ce.net \
    --to=ydroneaud@opteya.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.