From: Henrik Austad <henrik@austad.us>
To: Jiri Kosina <jkosina@suse.cz>, Rob Landley <rob@landley.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Updating 00-INDEX in Documentation/*
Date: Mon, 28 Oct 2013 14:05:11 +0100 [thread overview]
Message-ID: <20131028130511.GA6992@austad.us> (raw)
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
Hi Rob, Jiri
If this email goes the wrong place, my sincere apologies, my asbestos
underwear can be quickly donned!
I've been reading through some of the docs and one thing that has struct
me, is that there is a certain degree of bitrot (textrot?). Almost every
category has an outdated 00-INDEX. A couple of indexes has been updated
(thanks for applying Jiri!), but more remains.
This is obviously not the most important job to undertake, but it
serves as a very convenient starting-point when exploring a given topic.
Hacking away at python shows me that of the 254 subfolders 57 has outdated
00-INDEX, either with missing files, or files that has been removed. (see
list below)
Now, I'm quite happy to start fixing this, but what I would like to know
before I start:
- is it considered a waste of time? i.e. will it be worth the time
- what is best, a single, big patch, or a series of one patch per
directory?
- or should someone(tm) kick whoever caused 00-INDEX to be outdated, to fix
it?
thanks!
List of filesystems with outdated index
name of dir: (index_not_folder / in_folder_not_index)
filesystems: (5/17)
filesystems/nfs: (1/2)
m68k: (0/1)
serial: (1/2)
leds: (0/4)
arm: (10/7)
blackfin: (0/2)
ide: (1/1)
fb: (3/3)
networking: (3/12)
scsi: (0/8)
power: (1/2)
filesystems: (5/17)
filesystems/nfs: (1/2)
arm: (10/7)
RCU: (0/1)
mmc: (4/0)
fmc: (4/0)
w1: (2/0)
w1/masters: (1/2)
w1/slaves: (0/1)
timers: (0/3)
devicetree: (5/1)
serial: (1/2)
leds: (0/4)
arm: (10/7)
fb: (3/3)
power: (1/2)
mmc: (4/0)
w1: (2/0)
w1/masters: (1/2)
w1/slaves: (0/1)
powerpc: (4/0)
x86: (0/8)
PCI: (1/1)
isdn: (1/0)
powerpc: (4/0)
laptops: (1/2)
vm: (4/7)
virtual: (3/0)
scheduler: (0/1)
x86: (0/8)
s390: (2/2)
filesystems: (5/17)
filesystems/nfs: (1/2)
arm: (10/7)
serial: (1/2)
leds: (0/4)
arm: (10/7)
fb: (3/3)
power: (1/2)
mmc: (4/0)
w1: (2/0)
w1/masters: (1/2)
w1/slaves: (0/1)
powerpc: (4/0)
x86: (0/8)
--
Henrik Austad
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2013-10-28 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 13:05 Henrik Austad [this message]
2013-10-30 13:21 ` Updating 00-INDEX in Documentation/* Jiri Kosina
2013-11-15 5:09 ` Rob Landley
2013-11-19 0:03 ` Henrik Austad
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=20131028130511.GA6992@austad.us \
--to=henrik@austad.us \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).