From: Jonathan Nieder <jrnieder@gmail.com>
To: Yann Droneaud <ydroneaud@opteya.com>
Cc: Junio C Hamano <gitster@pobox.com>, Git <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation: add a README file
Date: Thu, 21 Mar 2013 15:09:06 -0700 [thread overview]
Message-ID: <20130321220906.GB12223@google.com> (raw)
In-Reply-To: <1363903193.6289.57.camel@test.quest-ce.net>
Yann Droneaud wrote:
> Anyway, having a README at the Documentation/ level could also help to
> explain what to be found in this directory:
> - user-manual
> - howto
> - technical
> - RelNote
> - SubmittingPatches
> - CodingGuidelines
> - etc.
A Documentation/README or Documentation/INDEX in the spirit of Linux's
Documentation/00-INDEX could be interesting if it does not bitrot
(unlike Linux's 00-INDEX). Presumably that means it would have to be
pretty brief.
Thanks,
Jonathan
prev parent reply other threads:[~2013-03-21 22:09 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
2013-03-21 21:59 ` Yann Droneaud
2013-03-21 22:09 ` Jonathan Nieder [this message]
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=20130321220906.GB12223@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ydroneaud@opteya.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).