All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] Stable kernel release process update
Date: Sat, 12 Mar 2022 15:00:39 +0700	[thread overview]
Message-ID: <20220312080043.37581-1-bagasdotme@gmail.com> (raw)

The stable release process documented in stable-kernel-rules.rst needs
to be updated to reflect current procedure.

Patch 1 is merely reorganizing three submission option lists to be
subsection of the procedure section.

Patch 2 contains the actual process documentation update.

Patch 3 and 4 updates "Tree" section by adding stable -rc tree link and
correcting link for stable tree, respectively.

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

Bagas Sanjaya (4):
  Documentation: make option lists subsection of "Procedure for
    submitting patches to the -stable tree" in stable-kernel-rules.rst
  Documentation: update stable review cycle documentation
  Documentation: add link to stable release candidate tree
  Documentation: update stable tree link

 Documentation/process/stable-kernel-rules.rst | 31 ++++++++++++++-----
 1 file changed, 24 insertions(+), 7 deletions(-)


base-commit: ffb217a13a2eaf6d5bd974fc83036a53ca69f1e2
-- 
An old man doll... just what I always wanted! - Clara


             reply	other threads:[~2022-03-12  8:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-12  8:00 Bagas Sanjaya [this message]
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
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=20220312080043.37581-1-bagasdotme@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --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.