From: Pavel Machek <pavel@ucw.cz>
To: "Andreas Weißel" <andreas.weissel@gmail.com>
Cc: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] Super long-term kernel support
Date: Mon, 23 Mar 2020 23:16:06 +0100 [thread overview]
Message-ID: <20200323221606.GA7808@duo.ucw.cz> (raw)
In-Reply-To: <CAC4QREfMtM1MQBVf2ZhRbBstUkCBbny5pwWEd_dJ09GcQpyiHA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 875 bytes --]
Hi!
> I have a question regarding the super long-term kernel support: can
> other commercial or non-commercial projects make use of such kernel
> versions like "linux-4.19.y-cip", i.e., use the CIP git repositories
> to address security issues (CVEs) in the Linux kernel even after the
> upstream long-term versions are no longer supported, or is this
> considered a service for members only?
Kernel is GPLed. If you get any version of kernel from anywhere, you
are basically welcome to use it any way you want. That's what GPL
says.
Check with your lawyers.
(Plus, CIP project is trying to be friendly member of community....)
Best regards,
Pavel
(Not a lawyer, not speaking for anyone but my horse.)
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev
next prev parent reply other threads:[~2020-03-23 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 16:54 [cip-dev] Super long-term kernel support Andreas Weißel
2020-03-23 22:16 ` Pavel Machek [this message]
2020-03-24 6:12 ` 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=20200323221606.GA7808@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=andreas.weissel@gmail.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