Re: [Ksummit-discuss] [CORE TOPIC] Issues with stable process

[Sasha Levin <sasha.levin@oracle.com>]

On 07/14/2015 11:38 AM, Steven Rostedt wrote:
> On Tue, 14 Jul 2015 11:32:27 -0400
> Sasha Levin <sasha.levin@oracle.com> wrote:
> 
>> > If there's an issue that causes that effect then the original commit that
>> > caused it should be reverted rather than introducing an untested fix right
>> > away.
>> > 
> You'd think. But there's been times that I sent a revert patch where
> Linus himself would just make the fix instead. So Linus is just as
> guilty as the rest of us for adding in patches that were not tested in
> -next.

I suppose it depends on how trivial the patch in: I'm not saying not to do
it for simple things (spelling errors, trivial compile failures and such), but
yes - if Linus prefers to pull a more than trivial untested change to fix a
bug that makes him as guilty as the rest of us.

The point I'm trying to make is that a bad patch in Linus' tree has a wider
ripple effect than what it were in the past, while Linus might consider a bad
patch in one of the -rc releases something minor since "no one should be using
it for production" it really isn't the case any more, those patches can and
will end up with the folks who don't want to have them.


Thanks,
Sasha