From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-doc@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] Documentation: add link to stable release candidate tree
Date: Sat, 12 Mar 2022 10:44:13 +0100 [thread overview]
Message-ID: <YixrbWkVPx76a/E5@kroah.com> (raw)
In-Reply-To: <20220312080043.37581-4-bagasdotme@gmail.com>
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@linuxfoundation.org>
> Cc: Sasha Levin <sashal@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: stable@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.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
next prev parent reply other threads:[~2022-03-12 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 8:00 [PATCH 0/4] Stable kernel release process update Bagas Sanjaya
2022-03-12 8:00 ` [PATCH 1/4] Documentation: make option lists subsection of "Procedure for submitting patches to the -stable tree" in stable-kernel-rules.rst Bagas Sanjaya
2022-03-12 9:42 ` Greg Kroah-Hartman
2022-03-14 6:39 ` Bagas Sanjaya
2022-03-12 8:00 ` [PATCH 2/4] Documentation: update stable review cycle documentation Bagas Sanjaya
2022-03-12 9:40 ` Greg Kroah-Hartman
2022-03-14 6:37 ` Bagas Sanjaya
2022-03-12 8:00 ` [PATCH 3/4] Documentation: add link to stable release candidate tree Bagas Sanjaya
2022-03-12 9:44 ` Greg Kroah-Hartman [this message]
2022-03-12 8:00 ` [PATCH 4/4] Documentation: update stable tree link Bagas Sanjaya
2022-03-12 9:41 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YixrbWkVPx76a/E5@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.