From: Jonathan Corbet <corbet@lwn.net>
To: Henrik Austad <henrik@austad.us>
Cc: Joe Perches <joe@perches.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC] Drop all 00-INDEX files from Documentation/
Date: Mon, 3 Sep 2018 12:45:45 -0600 [thread overview]
Message-ID: <20180903124545.089ead51@lwn.net> (raw)
In-Reply-To: <20180903105542.GA9485@sisyphus.home.austad.us>
On Mon, 3 Sep 2018 12:55:42 +0200
Henrik Austad <henrik@austad.us> wrote:
> On Wed, Aug 29, 2018 at 09:20:30AM -0700, Joe Perches wrote:
> > On Wed, 2018-08-29 at 14:28 +0200, Henrik Austad wrote:
> > > The 00-INDEX files are supposed to give a summary of all files present
> > > in a directory, but these files are horribly out of date and their
> > > usefulness is brought into question.
> > >
> > > A few years back it was mentioned that these files were no longer
> > > needed, and they have since then grown further out of date, so perhaps
> > > it is time to just throw them out.
> >
> > Good idea.
> >
> > .rst is becoming more common and these 00-INDEX files
> > are unnecessary and occasionally misleading.
>
> Ok, should I respin and clean up all the other files referencing 00-INDEX
> and send to a wider audience?
Wider audience might be good. I've not yet decided whether I think this
is a good idea or not. We certainly don't need those files for stuff
that's in the RST doctree, that's what the index.rst files are for. But I
suspect some people might complain about losing them for the rest of the
content. I do get patches from people updating them, so some folks do
indeed look at them...
jon
next prev parent reply other threads:[~2018-09-03 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 12:28 [PATCH] [RFC] Drop all 00-INDEX files from Documentation/ Henrik Austad
2018-08-29 16:20 ` Joe Perches
2018-09-03 10:55 ` Henrik Austad
2018-09-03 18:45 ` Jonathan Corbet [this message]
2018-09-03 20:32 ` 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=20180903124545.089ead51@lwn.net \
--to=corbet@lwn.net \
--cc=henrik@austad.us \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).