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: <87cy7i8tsj.fsf@trenco.lwn.net>
Date: Mon, 22 Sep 2025 08:07:40 -0600
From: Jonathan Corbet <corbet@....net>
To: Bagas Sanjaya <bagasdotme@...il.com>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Documentation
 <linux-doc@...r.kernel.org>, Linux Kernel Workflows
 <workflows@...r.kernel.org>
Cc: Dante Strock <dantestrock@...mail.com>, Randy Dunlap
 <rdunlap@...radead.org>
Subject: Re: [PATCH v2] Documentation: process: Arbitrarily bump kernel
 major version number

Bagas Sanjaya <bagasdotme@...il.com> writes:

> On 9/22/25 19:53, Jonathan Corbet wrote:
>> Bagas Sanjaya <bagasdotme@...il.com> writes:
>> 
>>> The big picture section of 2.Process.rst currently hardcodes major
>>> version number to 5 since fb0e0ffe7fc8e0 ("Documentation: bring process
>>> docs up to date"). As it can get outdated when it is actually
>>> incremented (the recent is 6 and will be 7 in the near future),
>>> arbitrarily bump it to 9, giving a headroom for a decade.
>>>
>>> Note that the version number examples are kept to illustrate the
>>> numbering scheme.
>>>
>>> Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
>> 
>> Just FYI, I've pretty much shut docs down for the upcoming merge window.
>> I'm probably not the only one.
>> 
>
> So it is slated for 6.19 then?

If it's not in docs-next (or some other subsystem tree) now then yes, it
will wait another cycle.  We are at -rc7, after all.

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ