1 |
On Tue, Sep 27, 2011 at 11:33 AM, Michael Mol <mikemol@×××××.com> wrote: |
2 |
> On Tue, Sep 27, 2011 at 2:24 PM, Mark Knecht <markknecht@×××××.com> wrote: |
3 |
<SNIP> |
4 |
>> I can pretty much promise you that one area likely to get LOTS of |
5 |
>> attention in this kernel series IS security updates, at least if they |
6 |
>> are kernel based security issues. That a major reason, if not the #1 |
7 |
>> reason, that this series of kernels exists. |
8 |
> |
9 |
> And I think that's excellent; I wasn't even aware of them until today. |
10 |
> |
11 |
|
12 |
I understand you weren't aware so I'm just trying to gently help you |
13 |
and others understand why this series exists. |
14 |
|
15 |
If you read through the requirements for submitting patches to the |
16 |
long term stable series one point is that an identical/similar patch |
17 |
must exist in the development tree. For security issues those are |
18 |
addressed pretty quickly, and as long as the code works in the earlier |
19 |
code it's conceptually pretty easy for someone to get it included in |
20 |
the long term series. Of course, I'm not a developer so I don't know |
21 |
what is _really_ required, but conceptually it's doable. |
22 |
|
23 |
Cheers, |
24 |
Mark |