lkml.org 
[lkml]   [2018]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH AUTOSEL for 4.14 015/161] printk: Add console owner and waiter logic to load balance console writes
On Mon, 16 Apr 2018, Sasha Levin wrote:

> I agree that as an enterprise distro taking everything from -stable
> isn't the best idea. Ideally you'd want to be close to the first
> extreme you've mentioned and only take commits if customers are asking
> you to do so.
>
> I think that the rule we're trying to agree upon is the "It must fix
> a real bug that bothers people".
>
> I think that we can agree that it's impossible to expect every single
> Linux user to go on LKML and complain about a bug he encountered, so the
> rule quickly becomes "It must fix a real bug that can bother people".

So is there a reason why stable couldn't become some hybrid-form union of

- really critical issues (data corruption, boot issues, severe security
issues) taken from bleeding edge upstream
- [reviewed] cherry-picks of functional fixes from major distro kernels
(based on that very -stable release), as that's apparently what people
are hitting in the real world with that particular kernel

?

Thanks,

--
Jiri Kosina
SUSE Labs

\
 
 \ /
  Last update: 2018-04-16 23:29    [W:0.164 / U:2.352 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site