From: "Kadel, Michael" <michael.kadel@karlstorz.com>
To: cip-dev@lists.cip-project.org
Subject: Re: projected EOL v4.4 SLTS
Date: Mon, 02 Oct 2023 04:59:57 -0700 [thread overview]
Message-ID: <27529.1696247997132604008@lists.cip-project.org> (raw)
In-Reply-To: <4785f4d6-3bd4-4f98-92b9-77e705f4bd95@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
Hi Jan,
what is necessary in terms of resources and budget for us as a company
to extend the Linux Kernel v4.4 i.e. for further 5 years (EOL 2032)?
More precise, how many FTEs should work on this kernel extension
and is it also possible to purchase such a service by the CIP?
Michael
[-- Attachment #2: Type: text/html, Size: 340 bytes --]
next prev parent reply other threads:[~2023-10-02 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 14:10 projected EOL v4.4 SLTS Kadel, Michael
2023-09-26 13:53 ` Jan Kiszka
2023-09-27 7:28 ` Kadel, Michael
2023-09-28 6:52 ` Jan Kiszka
2023-10-02 11:59 ` Kadel, Michael [this message]
2023-10-03 20:26 ` Jan Kiszka
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=27529.1696247997132604008@lists.cip-project.org \
--to=michael.kadel@karlstorz.com \
--cc=cip-dev@lists.cip-project.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