linux-kernel - Re: [RFC PATCH] doc: change the way how the stable backport is requested

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20161205131557.GA23899@1wt.eu>
Date:   Mon, 5 Dec 2016 14:15:57 +0100
From:   Willy Tarreau <w@....eu>
To:     Michal Hocko <mhocko@...nel.org>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Stable tree <stable@...r.kernel.org>,
        Andy Lutomirski <luto@...capital.net>,
        Jiri Kosina <jkosina@...e.cz>
Subject: Re: [RFC PATCH] doc: change the way how the stable backport is
 requested

Hi Michal,

On Mon, Dec 05, 2016 at 02:05:08PM +0100, Michal Hocko wrote:
> > That's not a problem in that I know I like to see them to give me a
> > "heads up" that something is coming down the pipeline soon.
> 
> Are you really tracking all those discussion to catch resulting patches
> in the Linus' tree? I simply fail to see a point having N versions of
> the patch on the stable mailing list before it gets picked up from the
> _Linus'_ anyayw.
> 
> > I don't think anyone has ever complained of this before, do you?
> 
> This is the reason I have stopped following the stable mailing list.
> The noise level is just too high.

I personally have mixed opinion on this. I agree that there's too much
"noise" on the list, but at the same time I would probably be even more
clueless about patches I receive if I didn't have this noise. As Greg
says, these emails tell you something is coming. For sure I don't keep
track of the discussions nor the threads but sometimes I'm interested
in reading them and that makes my later job easier.

So in the end, I just press ",st" in mutt and all stable mails are moved
away from my mbox and archived into the stable box. My only risk at the
moment is to accidently miss something that people expected me to merge
by sending it to stable only, but that doesn't happen often.

So I think I'm fine with not changing anything as well.

cheers,
Willy