From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>,
Sasha Levin <sashal@kernel.org>, Tyler Hicks <code@tyhicks.com>
Subject: Re: [PATCH v2] Documentation: process: replace outdated LTS table w/ link
Date: Tue, 18 Oct 2022 10:33:07 +0700 [thread overview]
Message-ID: <e43b596e-e5e1-d928-241f-b89f2861cbea@gmail.com> (raw)
In-Reply-To: <CAKwvOd=L7i6iMZ6CRKWpY1yzg5QZj5FM7Rd1HtVFj-6J-qdPtQ@mail.gmail.com>
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
next prev parent reply other threads:[~2022-10-18 3:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:34 [PATCH] Documentation: process: update the list of current LTS Nick Desaulniers
2022-10-14 2:24 ` Bagas Sanjaya
2022-10-14 7:08 ` Greg Kroah-Hartman
2022-10-14 16:34 ` Tyler Hicks
2022-10-14 16:46 ` Greg Kroah-Hartman
2022-10-14 17:10 ` [PATCH v2] Documentation: process: replace outdated LTS table w/ link Nick Desaulniers
2022-10-14 17:13 ` Tyler Hicks
2022-10-14 17:41 ` Greg Kroah-Hartman
2022-10-15 2:06 ` Bagas Sanjaya
2022-10-18 0:04 ` Nick Desaulniers
2022-10-18 3:33 ` Bagas Sanjaya [this message]
2022-10-18 21:44 ` Jonathan Corbet
2022-10-22 3:27 ` Bagas Sanjaya
2022-10-14 7:08 ` [PATCH] Documentation: process: update the list of current LTS 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=e43b596e-e5e1-d928-241f-b89f2861cbea@gmail.com \
--to=bagasdotme@gmail.com \
--cc=ben@decadent.org.uk \
--cc=code@tyhicks.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).