linux-kernel - Re: linux-next: Tree for Sep 21

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]

Date:   Fri, 23 Sep 2016 11:24:04 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     linux-next <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Sep 21

On Tue, Sep 20, 2016 at 11:08 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Changes since 20160920:
> [...]
> Non-merge commits (relative to Linus' tree): 11180
>  8424 files changed, 456474 insertions(+), 237951 deletions(-)

What happened here? The previous linux-next tree was much smaller. The
"changes since" part doesn't actually talk about the almost 3000 new
non-merge commits that very suddenly showed up.

I wonder if your automation could add some notes on things like this
when clearly one of the trees changes radically. Back in 20160920,
linux-next looked fairly small compared to previous releases. And then
the next day it suddenly looked quite big.

I get the feeling that several thousand new commits just before the
merge window opens is not a good sign. Of course, I'm planning an rc8
this time around anyway, but even so this is pretty surprising.

           Linus