On 12/04/16 13:52, Willy Tarreau wrote:
On Tue, Apr 12, 2016 at 01:31:21PM +0100, Eddie Chapman wrote:
None-the-less, I applaud and thank Sasha for this new effort, and I
personally will find it very useful. Yes, the lines between bug fix and
security fix are very blurred, and so this tree won
Hi Eddie,
On Tue, Apr 12, 2016 at 01:31:21PM +0100, Eddie Chapman wrote:
> None-the-less, I applaud and thank Sasha for this new effort, and I
> personally will find it very useful. Yes, the lines between bug fix and
> security fix are very blurred, and so this tree won't have every "security"
>
I'd like to add my 2c here as a mere user of many of the stable trees
for many years in my projects.
The stable trees are excellent. The quality of the people selecting
patches and the selection process is excellent. I've rarely been on the
bad end of a regression. I've always used stable ker
On Mon, Apr 11, 2016 at 11:35:08PM -0700, Greg KH wrote:
> On Tue, Apr 12, 2016 at 08:22:37AM +0200, Willy Tarreau wrote:
> > I think we may have more of an issue educating our users than an issue
> > with the code we distribute.
>
> I think that's the issue here, combined with users that just don
On Tue, Apr 12, 2016 at 08:22:37AM +0200, Willy Tarreau wrote:
> I think we may have more of an issue educating our users than an issue
> with the code we distribute.
I think that's the issue here, combined with users that just don't want
to upgrade as it's "hard" for them. There's nothing we can
On Mon, Apr 11, 2016 at 06:48:32PM -0400, Sasha Levin wrote:
> As this suggests, we don't only fix bugs in stable trees, we also introduce
> a fair amount of new ones.
Sure, and the older the kernel, the higher the number of bugs reintroduced
due to a faulty backport (often relying on a missing pa
On 04/11/2016 05:17 PM, Willy Tarreau wrote:
> Hi Sasha,
>
> On Mon, Apr 11, 2016 at 04:38:17PM -0400, Sasha Levin wrote:
>>> How are you
>>> going to judge which driver fixes to take and which not to? Why not
>>> take them all if they fix bugs?
>>
>> Because some fixes introduce bug on their own
Hi Sasha,
On Mon, Apr 11, 2016 at 04:38:17PM -0400, Sasha Levin wrote:
> > How are you
> > going to judge which driver fixes to take and which not to? Why not
> > take them all if they fix bugs?
>
> Because some fixes introduce bug on their own? Take a look at how many
> commits in the stable tr
On 04/11/2016 04:09 PM, Greg KH wrote:
> On Mon, Apr 11, 2016 at 02:58:37PM -0400, Sasha Levin wrote:
>> On 04/11/2016 02:41 PM, Greg KH wrote:
>>> On Mon, Apr 11, 2016 at 01:53:41PM -0400, Sasha Levin wrote:
Quite a few users of the stable trees pointed out that on complex
deployments,
On Mon, Apr 11, 2016 at 02:58:37PM -0400, Sasha Levin wrote:
> On 04/11/2016 02:41 PM, Greg KH wrote:
> > On Mon, Apr 11, 2016 at 01:53:41PM -0400, Sasha Levin wrote:
> >> Hi all,
> >>
> >>
> >> I'd like to announce the linux-stable security tree project. The purpose
> >> is to create a derivative
On 4/11/16, Sasha Levin wrote:
> On 04/11/2016 02:34 PM, Jeff Merkey wrote:
>> On 4/11/16, Sasha Levin wrote:
>>> Hi all,
>>>
>>>
>>> I'd like to announce the linux-stable security tree project. The purpose
>>> is to create a derivative tree from the regular stable tree that would
>>> contain onl
On 04/11/2016 02:34 PM, Jeff Merkey wrote:
> On 4/11/16, Sasha Levin wrote:
>> Hi all,
>>
>>
>> I'd like to announce the linux-stable security tree project. The purpose
>> is to create a derivative tree from the regular stable tree that would
>> contain only commits that fix security vulnerabiliti
On Mon, Apr 11, 2016 at 8:34 PM, Jeff Merkey wrote:
> On 4/11/16, Sasha Levin wrote:
>> Hi all,
>>
>>
>> I'd like to announce the linux-stable security tree project. The purpose
>> is to create a derivative tree from the regular stable tree that would
>> contain only commits that fix security vul
On 04/11/2016 02:17 PM, Jeff Merkey wrote:
> On 4/11/16, Sasha Levin wrote:
>> Hi all,
>>
>>
>> I'd like to announce the linux-stable security tree project. The purpose
>> is to create a derivative tree from the regular stable tree that would
>> contain only commits that fix security vulnerabiliti
On 04/11/2016 02:41 PM, Greg KH wrote:
> On Mon, Apr 11, 2016 at 01:53:41PM -0400, Sasha Levin wrote:
>> Hi all,
>>
>>
>> I'd like to announce the linux-stable security tree project. The purpose
>> is to create a derivative tree from the regular stable tree that would
>> contain only commits that f
On Mon, Apr 11, 2016 at 01:53:41PM -0400, Sasha Levin wrote:
> Hi all,
>
>
> I'd like to announce the linux-stable security tree project. The purpose
> is to create a derivative tree from the regular stable tree that would
> contain only commits that fix security vulnerabilities.
And how are you
On 4/11/16, Sasha Levin wrote:
> Hi all,
>
>
> I'd like to announce the linux-stable security tree project. The purpose
> is to create a derivative tree from the regular stable tree that would
> contain only commits that fix security vulnerabilities.
>
> Quite a few users of the stable trees point
On 4/11/16, Sasha Levin wrote:
> Hi all,
>
>
> I'd like to announce the linux-stable security tree project. The purpose
> is to create a derivative tree from the regular stable tree that would
> contain only commits that fix security vulnerabilities.
>
> Quite a few users of the stable trees point
18 matches
Mail list logo
