linux-kernel - Re: [PATCH 0/4] Docs/mm: rename legacy docs to unsorted docs

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87jzi2t8wq.fsf@trenco.lwn.net>
Date: Wed, 03 Jul 2024 16:20:21 -0600
From: Jonathan Corbet <corbet@....net>
To: SeongJae Park <sj@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>
Cc: SeongJae Park <sj@...nel.org>, Kent Overstreet
 <kent.overstreet@...ux.dev>, Suren Baghdasaryan <surenb@...gle.com>,
 linux-mm@...ck.org, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] Docs/mm: rename legacy docs to unsorted docs

SeongJae Park <sj@...nel.org> writes:

> The work for changing the memory mangement documentation outline has
> started from 2022.  For that, old documents have placed under new
> chapter, "Legacy Documentations".  The plan is to eventually move all
> old documentations into new outline, while asking new documents to be
> added on the new outline from the beginning.
>
> However, it is unclear where on the new outline each document should be
> placed for some cases.  Meanwhile, the name ("legacy") makes readers
> feel the documents under the chapter might be outdated or not actively
> maintained.  The absence of clear criteria for new outline also makes
> new documents difficult to find where those should be placed.  A new
> document was put on the bottom of the new outline recently, apparently
> not based on a clear guideline but just because it is the bottom of the
> list.
>
> Rename the "Legagy Documentation" chapter to "Unsorted Documentations"
> with minor fixups.

Series applied, thanks.

jon