From: Jonathan Corbet <corbet@lwn.net>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-doc@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Documentation/index.rst
Date: Sat, 16 Apr 2022 02:53:50 -0600 [thread overview]
Message-ID: <87mtgl2yu9.fsf@meer.lwn.net> (raw)
In-Reply-To: <YlPps05WaHH2ghmp@zn.tnic>
Borislav Petkov <bp@alien8.de> writes:
> So I was thinking that maybe there should be a small set of rules -
> don't want to overload submitters :) - about structure and formatting
> of each documentation section/file/etc so that the final product can be
> more useful and I can actually find something in there. :-)
Totally agreed.
When I took on Documentation/, it was one big pile of random stuff.
Since then, I've been pushing to organize things into various "books"
with some success, so that now we have several smaller piles of random
stuff. I do think it's an improvement, but the job is far from done.
$SOMEBODY really needs to do a pass over the top-level index.rst and
create some better order there, it's been a while. I'll try to get to
that soon (if nobody beats me to it - a likely outcome :), but it won't
be right away.
thanks,
jon
prev parent reply other threads:[~2022-04-16 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 8:41 Documentation/index.rst Borislav Petkov
2022-04-16 8:53 ` Jonathan Corbet [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=87mtgl2yu9.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bp@alien8.de \
--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).