From: Henrik Austad <henrik@austad.us>
To: Rob Landley <rob@landley.net>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Updating 00-INDEX in Documentation/*
Date: Tue, 19 Nov 2013 01:03:41 +0100 [thread overview]
Message-ID: <20131119000341.GA1218@austad.us> (raw)
In-Reply-To: <1384492143.1974.272@driftwood>
On Thu, Nov 14, 2013 at 11:09:03PM -0600, Rob Landley wrote:
> On 10/28/2013 08:05:11 AM, Henrik Austad wrote:
> >Hi Rob, Jiri
> >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)
>
> I'm a bit behind on my email just now. (Started a new job last
> month, everything else got derailed for a bit.)
>
> >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?
>
> Go for it.
Ok, I'll work my way through the list then.
> I've had a script that does this since 2007, but it's in the context of
> creating html indexes for the kernel.org/doc/Documentation directory
Hmm, ok, I was just planning to get the 00-INDEX files up to speed,
anything beyond that was not on my plan.
> , and after the kernel.org breakin they never gave me rsync access back
> (because it's not built into git and all any server ever does is run git,
> right?) so I couldn't update it anymore. Then they decided that the
> Documentation directory should just be a raw checkout from git with no
> html indexes (because git), and presumably they'll be doing the same for
> http://kernel.org/doc/menuconfig any day now (how, I couldn't tell you,
> but it's apparently no longer my problem)...
>
> So it's kinda hard to get enthused about it these days. I wanted to
> revive my old push to reorganize the documentation directory
> (https://lkml.org/lkml/2007/5/22/473 and such) but if the word from
> on high is that a giant raw pile of unsorted files is the optimal
> way to organize things, who am I to argue?
>
> Same problem for kernel.org/doc/htmldocs: the ones I did way back when
> (https://web.archive.org/web/20090327025639/http://www.kernel.org/doc/htmldocs/)
> had both the "one big html file" version and the lots of little files
> version and I'd watch the build logs and send patches to get the warnings
> down, but they took that away and replaced it without even letting me
> know they were doing that, so I've fallen out of the habit. (My
> understanding was that the kernel.org guys officially don't care about
> any data that isn't accessed through git, and a web browser isn't git,
> so...)
>
> *shrug* I suppose all it's still on the todo list somewhere. Maybe
> somewhere after reviving http://landley.net/qemu and catching that
> up to current, but it's in there...
>
> Rob
--
Henrik Austad
prev parent reply other threads:[~2013-11-19 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 13:05 Updating 00-INDEX in Documentation/* Henrik Austad
2013-10-30 13:21 ` Jiri Kosina
2013-11-15 5:09 ` Rob Landley
2013-11-19 0:03 ` Henrik Austad [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=20131119000341.GA1218@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).