From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Tudor Ambarus <tudor.ambarus@linaro.org>,
gregkh@linuxfoundation.org, sashal@kernel.org, corbet@lwn.net
Cc: stable@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, joneslee@google.com
Subject: Re: [PATCH] Documentation: stable: Add rule on what kind of patches are accepted
Date: Thu, 22 Dec 2022 19:56:57 +0700 [thread overview]
Message-ID: <4fbc9e89-24af-9d59-dab0-73925ac94df1@gmail.com> (raw)
In-Reply-To: <20221222091658.1975240-1-tudor.ambarus@linaro.org>
On 12/22/22 16:16, Tudor Ambarus wrote:
> The list of rules on what kind of patches are accepted, and which ones
> are not into the “-stable” tree, did not mention anything about new
> features and let the reader use its own judgement. One may be under the
> impression that new features are not accepted at all, but that's not true:
> new features are not accepted unless they fix a reported problem.
> Update documentation with missing rule.
>
Are there any other examples of problems that can "only" be solved by
introducing new features? Or new huge features that are virtually
harder to backport?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-12-22 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 9:16 Tudor Ambarus
2022-12-22 12:56 ` Bagas Sanjaya [this message]
2022-12-22 13:01 ` Tudor Ambarus
2022-12-23 1:55 ` Bagas Sanjaya
2022-12-22 13:32 ` Greg KH
2022-12-22 14:20 ` Tudor Ambarus
2022-12-22 16:24 ` Greg KH
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=4fbc9e89-24af-9d59-dab0-73925ac94df1@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=joneslee@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@linaro.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
all inboxes | Powered by JetHome®