linux-kernel - Re: [PATCH v2 0/3] docs: submit-checklist: structure by category

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]

Date: Thu, 29 Feb 2024 11:36:43 +0100
From: Lukas Bulwahn <lukas.bulwahn@...il.com>
To: Jani Nikula <jani.nikula@...el.com>
Cc: Jonathan Corbet <corbet@....net>, Randy Dunlap <rdunlap@...radead.org>, workflows@...r.kernel.org, 
	linux-doc@...r.kernel.org, kernel-janitors@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/3] docs: submit-checklist: structure by category

On Thu, Feb 29, 2024 at 11:25 AM Jani Nikula <jani.nikula@...el.com> wrote:
>
> On Thu, 29 Feb 2024, Lukas Bulwahn <lukas.bulwahn@...il.com> wrote:
> > from Jani Nikula:
> >   - turn categories into subheadings
> >   - use common heading adornment
> >   - change to bullet or autonumbered lists
> >   - propose those changes as separate additional patches
>
> I was hoping these cleanups would've come *first*, but up to Jon to
> decide if that really matters.
>

I see, changing to autonumbered lists could be done before, but the
subheadings only exist once reordered.

I am still in favor of the squashed commit: we are talking about a
very small document that central content has not been touched for a
long time. It is not code, where someone would bisect into. So, the
history does not need to carry every single stylistic change as yet
another commit.

Jani, I can do what you are asking for---but it is certainly going to
take yet a few hours to have the commits exactly into that form of
stylistic changes.

Let us see what Jon thinks.

Lukas