linux-kernel - Re: Documentation/index.rst

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87mtgl2yu9.fsf@meer.lwn.net>
Date:   Sat, 16 Apr 2022 02:53:50 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Borislav Petkov <bp@...en8.de>
Cc:     linux-doc@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: Documentation/index.rst

Borislav Petkov <bp@...en8.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