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: <df8c22fb-878a-3d98-4a9d-9000b4a2ffa7@gmail.com>
Date:   Thu, 25 Aug 2022 10:08:53 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Lukas Bulwahn <lukas.bulwahn@...il.com>,
        Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org,
        Tony Fischetti <tony.fischetti@...il.com>,
        Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH] docs: Update version number from 5.x to 6.x in README.rst

On 8/24/22 15:08, Lukas Bulwahn wrote:
> The description in 2.Process.rst is just a description of recent kernel
> releases, it was last updated in the beginning of 2020, and can be
> revisited at any time on a regular basis, independent of changing the
> version number from 5 to 6. So, there is no need to update this document
> now when transitioning from 5.x to 6.x numbering.
> 
The drawback of having quick list of recent kernel releases in 2.Process.rst
is that the list can be quickly outdated with newer releases, unless the list
is updated for every upcoming merge window.

There are two options:

  1. Programmatically generate the list, using last 5 mainline releases
     from Linus's tree, or
  2. Simply point to kernel.org frontpage

CC'ing Tony (since he last updated the list) and Randy Dunlap for suggestion.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ