From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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 1/4] Documentation: make option lists subsection of "Procedure for submitting patches to the -stable tree" in stable-kernel-rules.rst
Date: Mon, 14 Mar 2022 13:39:45 +0700 [thread overview]
Message-ID: <9564bb9c-e8f0-77fa-4464-144efc4854e8@gmail.com> (raw)
In-Reply-To: <YixrEFMkSZthmQpo@kroah.com>
On 12/03/22 16.42, Greg Kroah-Hartman wrote:
> On Sat, Mar 12, 2022 at 03:00:40PM +0700, Bagas Sanjaya wrote:
>> The table of contents generated for stable-kernel-rules.rst contains
>> "For all other submissions..." section, that includes options
>> subsections. These options subsections should have been subsections of
>> "Procedure for submitting patches..." section. Remove the redundant
>> section.
>
> The subject line is really long, was that intentional?
>
Yes, because I have to spell the full section name the option lists
I moved to.
>>
>> Also, convert note about security patches to use `.. note::` block.
>
> When you have an "also" that's a huge hint it should be a separate
> commit.
>
OK, will split.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-03-14 6:39 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 [this message]
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=9564bb9c-e8f0-77fa-4464-144efc4854e8@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.