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: <YixrbWkVPx76a/E5@kroah.com>
Date:   Sat, 12 Mar 2022 10:44:13 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     linux-doc@...r.kernel.org, Sasha Levin <sashal@...nel.org>,
        Jonathan Corbet <corbet@....net>, stable@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] Documentation: add link to stable release candidate
 tree

On Sat, Mar 12, 2022 at 03:00:42PM +0700, Bagas Sanjaya wrote:
> There is also stable release candidate tree. Mention it.
> 
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Cc: Sasha Levin <sashal@...nel.org>
> Cc: Jonathan Corbet <corbet@....net>
> Cc: stable@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
> ---
>  Documentation/process/stable-kernel-rules.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
> index c0c87d87f7d..523d2d35127 100644
> --- a/Documentation/process/stable-kernel-rules.rst
> +++ b/Documentation/process/stable-kernel-rules.rst
> @@ -183,6 +183,10 @@ Trees
>  
>  	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>  
> + - The release candidate of all stable kernel versions can be found at:
> +
> +        https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/
> +

Please add something here that says this tree will be rebased often and
should only be used for testing CI systems to pull from.  It is a
snapshot in time of the stable-queue.git tree and will change
frequently.

In short, I really don't like people using this tree, but have provided
it for those CI systems that don't like dealing with quilt patches only.

I also constantly forget to push the release tags to it, as I'm reminded
frequently :)

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ