From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-doc@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Dan Williams <dan.j.williams@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
Christian Brauner <brauner@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH] Documentation/process: Add Linux Kernel Contribution Maturity Model
Date: Fri, 16 Dec 2022 15:14:17 +0700 [thread overview]
Message-ID: <Y5wo2WblrsHpM8sH@debian.me> (raw)
In-Reply-To: <20221214185714.868374-1-tytso@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On Wed, Dec 14, 2022 at 01:57:14PM -0500, Theodore Ts'o wrote:
> +* Software Engineers are not allowed to contribute patches to the Linux
> + kernel.
Software engineers turned product manager or support desk people?
> + * The time interval between kernels used in the organization’s servers
> + and/or products, and the publication date of the upstream kernel
> + upon which the internal kernel is based.
I.e. the time for rebasing internal kernel against upstream one? For
example rebasing against several stable minor releases (x.y.z) is easier
than forward porting out-of-tree commits into new upstream release
(x.y).
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-12-16 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 18:57 [PATCH] Documentation/process: Add Linux Kernel Contribution Maturity Model Theodore Ts'o
2022-12-15 9:53 ` Michael S. Tsirkin
2022-12-15 15:14 ` Linus Walleij
2022-12-16 8:23 ` Bagas Sanjaya
2022-12-16 8:14 ` Bagas Sanjaya [this message]
2022-12-16 14:34 ` [PATCH] " Theodore Ts'o
2022-12-27 19:12 ` Florian Fainelli
2023-02-08 20:31 ` Jonathan Corbet
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=Y5wo2WblrsHpM8sH@debian.me \
--to=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=tytso@mit.edu \
/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).