From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to locally maintain an end-of-life kernel branch?
Date: Tue, 17 May 2016 12:31:34 -0700 [thread overview]
Message-ID: <20160517193134.GA14067@kroah.com> (raw)
In-Reply-To: <CADOUqRf8+=A1ED4su62Mcpz-vvTtST3g8L+pAWbQqY2omwX1rQ@mail.gmail.com>
On Tue, May 17, 2016 at 11:21:52AM -0700, Michael Harless wrote:
> Hi,?
>
> Sorry if this is covered somewhere, I haven't been able to find much yet in my
> searches.
>
> I'm working on a project using the LTS 3.14 kernel, but I'll need to be
> supporting it long after official support ends on kernel.org for the branch.?
Eeek, why? What is keeping you from moving to a newer kernel version?
Why is sticking with 3.14 a good idea for anyone?
> Are there any pointers or suggestions on how to monitor for security and bug
> fixes that I'll need to pull in and merge myself?
Look at the patches that are marked "cc: stable at vger.kernel.org" in the
changelog area when they hit Linus's tree. Or look at the patches that
I apply to the latest stable tree. Either way, be prepared to wade
through 100+ patches a week.
I'd recommend just updating to 4.1-stable, it will be easier and cheaper
for you in the long run.
good luck!
greg k-h
next prev parent reply other threads:[~2016-05-17 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 18:21 How to locally maintain an end-of-life kernel branch? Michael Harless
2016-05-17 19:31 ` Greg KH [this message]
2016-05-17 20:09 ` Michael Harless
2016-05-17 20:27 ` Valdis.Kletnieks at vt.edu
2016-05-17 20:48 ` Greg KH
2016-05-17 20:53 ` Michael Harless
2016-05-17 20:50 ` 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=20160517193134.GA14067@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).