All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Aaron Gray <aaronngray.lists@gmail.com>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Can we please have a major fork of Linux into a modern and legacy versions ?
Date: Sat, 9 Dec 2023 19:59:00 +0100	[thread overview]
Message-ID: <ZXS49NPio5oLPvit@duo.ucw.cz> (raw)
In-Reply-To: <ZWJm-6elPNNtbNI5@mit.edu>

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

Hi!

> > I hear Linux is going to drop a lot of legacy devices including the
> > ones dropped already. I am wondering if we can please have a major
> > fork of Linux into a modern and legacy versions ?
> > 
> > With a consolidation and security updates to the older version.
> 
> If someone wants to take an LTS kernel and volunteer to maintain it,
> including cherrypicking security updates, and making sure that fixes
> in core subsystems don't cause some of these legacy drivers to break,
> anyone can create such a fork.

CIP project is maintaining 4.4 and 4.19 kernels, and will do so for
... few more years. Our trees are here:
https://gitlab.com/cip-project/

Best regards,
								Pavel
-- 
People of Russia, stop Putin before his war on Ukraine escalates.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2023-12-09 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25 20:30 Can we please have a major fork of Linux into a modern and legacy versions ? Aaron Gray
2023-11-25 21:28 ` Theodore Ts'o
2023-12-09 18:59   ` Pavel Machek [this message]

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=ZXS49NPio5oLPvit@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=aaronngray.lists@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.