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 16:49:47 +0100	[thread overview]
Message-ID: <64e67681cf5584b51bc84082fe6304c0@meuh.org> (raw)
In-Reply-To: <7v8v5gbwh6.fsf@alter.siamese.dyndns.org>

Le 21.03.2013 16:31, Junio C Hamano a écrit :
> Yann Droneaud <ydroneaud@opteya.com> writes:
>
>> The documentation is in AsciiDoc format: it should be written 
>> somewhere
>> with links to AsciiDoc documentation so that it became easy to find
>> how to write documentation for Git.
>
> Certainly this does not deserve a *new* file to hold it.

That's the first one I look for.

There were no indication about how to write documentation
in SubmittingPatches.

Later, I've found the only useful piece of advice regarding the 
documentation
in howto/new-command.txt:

"
What every extension command needs
----------------------------------

You must have a man page, written in asciidoc (this is what Git help
followed by your subcommand name will display).  Be aware that there is
a local asciidoc configuration and macros which you should use.  It's
often helpful to start by cloning an existing page and replacing the
text content.
"

And I was grep'ing for ascii[ _-]doc throughout the sources !

> Isn't this inferrable from the top-level INSTALL already?

In short: No.

You want me to look in the INSTALL file to search for the syntax
to write documentation ?

For someone who don't follow Git development, it's really not the file 
you're looking for.

Regards.

-- 
Yann Droneaud
OPTEYA

  reply	other threads:[~2013-03-21 16:13 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 [this message]
2013-03-21 17:39     ` Junio C Hamano
2013-03-21 21:16       ` Junio C Hamano
2013-03-21 22:02         ` Yann Droneaud
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=64e67681cf5584b51bc84082fe6304c0@meuh.org \
    --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.