From: Randy Dunlap <rdunlap@infradead.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-doc@vger.kernel.org, Rob Landley <rob@landley.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: update top level 00-INDEX file with new additions
Date: Mon, 18 Feb 2013 07:57:36 -0800 [thread overview]
Message-ID: <51224F70.9050806@infradead.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1302181039000.17024@pobox.suse.cz>
On 02/18/13 01:39, Jiri Kosina wrote:
> On Thu, 14 Feb 2013, Paul Gortmaker wrote:
>
>> It seems there are about 80 new, but undocumented addtions at
>> the top level Documentation directory. This fixes up the top
>> level 00-INDEX by adding new entries and deleting a couple orphans.
>> Some subdirs could probably still use a check/cleanup too though.
After this patch, I would prefer to see a requirement that each Documentation/
file contain a "topic" line and then generate INDEX files from those automatically...
comments?
>> Acked-by: Rob Landley <rob@landley.net>
>> Cc: Jiri Kosina <trivial@kernel.org>
>> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>> ---
>>
>> [vectoring this via trivial tree as requested by Rob]
>
> Applied, thanks.
--
~Randy
next prev parent reply other threads:[~2013-02-18 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 20:20 [PATCH] Documentation: update top level 00-INDEX file with new additions Paul Gortmaker
2013-02-18 9:39 ` Jiri Kosina
2013-02-18 15:57 ` Randy Dunlap [this message]
2013-02-19 14:53 ` Paul Gortmaker
2013-02-21 5:32 ` Rob Landley
2013-02-21 21:31 ` Jiri Kosina
2013-02-23 19:19 ` Rob Landley
2013-02-19 17:44 ` Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2013-01-29 15:34 Paul Gortmaker
2013-02-07 5:28 ` Rob Landley
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=51224F70.9050806@infradead.org \
--to=rdunlap@infradead.org \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rob@landley.net \
/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.