linux-kernel - Re: [PATCH v2] Documentation: process: replace outdated LTS table w/ link

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: <e43b596e-e5e1-d928-241f-b89f2861cbea@gmail.com>
Date:   Tue, 18 Oct 2022 10:33:07 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Nick Desaulniers <ndesaulniers@...gle.com>
Cc:     Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        stable@...r.kernel.org, Ben Hutchings <ben@...adent.org.uk>,
        Sasha Levin <sashal@...nel.org>, Tyler Hicks <code@...icks.com>
Subject: Re: [PATCH v2] Documentation: process: replace outdated LTS table w/
 link

On 10/18/22 07:04, Nick Desaulniers wrote:
>> Should this patch be backported to all stable releases? I see Cc: stable
>> on message header, but not in the patch trailer.
> 
> I don't think so; unless people read stable versions of the
> documentation rather than HEAD?
> Perhaps I didn't need to cc stable, but I think that's ok for
> notifying people who are interested in stable, not necessarily
> strictly for backports?
> Either way, thanks again for the reviews+suggestions.
> 

I think most people will simply read the documentation from master branch
(as in docs.kernel.org).

Thanks.

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