From: Josh Triplett <josh@joshtriplett.org>
To: Henrik Austad <henrik@austad.us>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC v2] Drop all 00-INDEX files from Documentation/
Date: Mon, 3 Sep 2018 19:45:35 -0700 [thread overview]
Message-ID: <20180904024534.GA29802@localhost> (raw)
In-Reply-To: <1536012923-16275-1-git-send-email-henrik@austad.us>
[Trimming to author, linux-doc, and LKML for response.]
On Tue, Sep 04, 2018 at 12:15:23AM +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. Often a simple "ls" would reveal
> the same information as the filenames are generally quite descriptive as
> a short introduction to what the file covers (it should not surprise
> anyone what Documentation/sched/sched-design-CFS.txt covers)
>
> A few years back it was mentioned that these files were no longer really
> needed, and they have since then grown further out of date, so perhaps
> it is time to just throw them out.
[...]
> As a starting point, remove all index-files and references to 00-INDEX and
> see where the discussion is going.
Yes please.
I was *briefly* tempted, reading through the files, to suggest ensuring
that the one-line descriptions from the 00-INDEX files end up in the
documents themselves, but the more I think about it, I don't think even
that is worth anyone's time to do.
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
next prev parent reply other threads:[~2018-09-04 2:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 22:15 [PATCH] [RFC v2] Drop all 00-INDEX files from Documentation/ Henrik Austad
2018-09-03 22:15 ` Henrik Austad
2018-09-03 22:15 ` Henrik Austad
2018-09-04 2:45 ` Josh Triplett [this message]
2018-09-04 10:41 ` Mark Brown
2018-09-04 10:41 ` Mark Brown
2018-09-04 11:30 ` Pavel Machek
2018-09-04 11:30 ` Pavel Machek
2018-09-04 13:59 ` Steven Rostedt
2018-09-04 13:59 ` Steven Rostedt
2018-09-04 13:59 ` Steven Rostedt
2018-09-06 15:58 ` Jonathan Corbet
2018-09-06 15:58 ` Jonathan Corbet
2018-09-06 15:58 ` Jonathan Corbet
2018-09-06 16:01 ` Steven Rostedt
2018-09-06 16:01 ` Steven Rostedt
2018-09-06 16:01 ` Steven Rostedt
2018-09-06 21:39 ` Daniel Vetter
2018-09-06 21:39 ` Daniel Vetter
2018-09-06 21:39 ` Daniel Vetter
2018-09-07 7:21 ` Greg Kroah-Hartman
2018-09-07 7:21 ` Greg Kroah-Hartman
2018-09-07 7:21 ` Greg Kroah-Hartman
2018-09-04 13:02 ` Paul E. McKenney
2018-09-04 13:02 ` Paul E. McKenney
2018-09-04 15:45 ` Jens Axboe
2018-09-04 15:45 ` Jens Axboe
2018-09-04 17:56 ` Mike Rapoport
2018-09-04 17:56 ` Mike Rapoport
2018-09-05 11:42 ` Paul Moore
2018-09-05 11:42 ` Paul Moore
2018-09-05 11:42 ` Paul Moore
2018-09-09 21:12 ` Jonathan Corbet
2018-09-09 21:12 ` Jonathan Corbet
2018-09-09 21:12 ` Jonathan Corbet
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=20180904024534.GA29802@localhost \
--to=josh@joshtriplett.org \
--cc=henrik@austad.us \
--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 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.