linux-kernel - Re: [GIT PULL] Networking for 5.11-rc4

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: <20210114143352.7bfe4b94@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Thu, 14 Jan 2021 14:33:52 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     David Miller <davem@...emloft.net>,
        Netdev <netdev@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Networking for 5.11-rc4

On Thu, 14 Jan 2021 13:37:17 -0800 Linus Torvalds wrote:
> On Thu, Jan 14, 2021 at 12:05 PM Jakub Kicinski <kuba@...nel.org> wrote:
> >
> > Current release - regressions:
> >  ...
> > Current release - always broken:  
> 
> So I understand what you mean, but it does sound odd with that
> "Current release - always broken" thing not being a regression. The
> "always broken" makes it sound like it's some old broken code that has
> never worked, which it clearly isn't.
> 
> Maybe rephrase it as "new code bugs" or something? You've done that
> before ("bugs in new features").
> 
> I left it alone in the merge message, since we've had that pattern of
> speech before, but for some reason I reacted to it this time.

Will do, I succumbed to the lure of matching "Previous releases -
always broken".