From: Rob Landley <rob@landley.net>
To: Henrik Austad <henrik@austad.us>,
LKML doc <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Jiri Kosina <jkosina@suse.cz>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Mark Brown <broonie@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@elte.hu>, Gleb Natapov <gleb@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Len Brown <len.brown@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
James Bottomley <JBottomley@parallels.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [PATCH] Documentation cleanup, update 00-INDEX files in Documentation/
Date: Wed, 29 Jan 2014 22:24:11 -0600 [thread overview]
Message-ID: <52E9D3EB.1060209@landley.net> (raw)
In-Reply-To: <1391041675-31683-1-git-send-email-henrik@austad.us>
On 01/29/14 18:27, Henrik Austad wrote:
> Some of the 00-INDEX files are somewhat outdated and some folders does not
> contain 00-INDEX at all. Only outdated (with the notably exception of
> spi) indexes are touched here, the 169 folders without 00-INDEX has not
> been touched.
>
> This applies to Linus' tip (0e47c969).
Looks like an improvement.
Acked-by: Rob Landley <rob@landley.net>
(My own scripts to find this stuff are based on maintaining
http://kernel.org/doc and the kernel developers are no longer capable of
providing rsync access to that, despite repeated requests. Most recently
https://bugzilla.kernel.org/show_bug.cgi?id=52721 )
However, I'm curious about this bit:
> --- a/Documentation/00-INDEX
> +++ b/Documentation/00-INDEX
> @@ -1,11 +1,11 @@
>
> -This is a brief list of all the files in ./linux/Documentation and what
> -they contain. If you add a documentation file, please list it here in
> -alphabetical order as well, or risk being hunted down like a rabid dog.
> -Please keep the descriptions small enough to fit on one line.
> - Thanks -- Paul G.
> +# This is a brief list of all the files in ./linux/Documentation and what
> +# they contain. If you add a documentation file, please list it here in
> +# alphabetical order as well, or risk being hunted down like a rabid dog.
> +# Please keep the descriptions small enough to fit on one line.
> +# Thanks -- Paul G.
>
> -Following translations are available on the WWW:
> +# Following translations are available on the WWW:
Is there a reason for that?
Rob
next prev parent reply other threads:[~2014-01-30 4:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 0:27 [PATCH] Documentation cleanup, update 00-INDEX files in Documentation/ Henrik Austad
2014-01-30 2:25 ` Paul E. McKenney
2014-01-30 4:24 ` Rob Landley [this message]
2014-01-30 7:33 ` Henrik Austad
2014-01-31 22:24 ` Andrew Morton
2014-02-01 16:50 ` Henrik Austad
2014-02-02 7:04 ` Rob Landley
2014-02-02 18:09 ` James Bottomley
2014-02-12 2:35 ` Paul Gortmaker
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=52E9D3EB.1060209@landley.net \
--to=rob@landley.net \
--cc=JBottomley@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=gleb@kernel.org \
--cc=henrik@austad.us \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=plagnioj@jcrosoft.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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