netdev - Re: [PULL] Networking for v6.2-rc5

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] [day] [month] [year] [list]

Message-ID: <CAHk-=whEAtZ+p0svZ1i1jg3=bh2MWPm_KQo9Mq3AiKwKWaNHxQ@mail.gmail.com>
Date:   Fri, 20 Jan 2023 11:20:49 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     davem@...emloft.net, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, pabeni@...hat.com
Subject: Re: [PULL] Networking for v6.2-rc5

On Fri, Jan 20, 2023 at 9:30 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> So I undid my pull and will do your v2,

Side note: that late merge, and its revert is pretty ugly.

It seems to be a pattern that the networking tree has, which is not a
great sign (merging much too eargerly into the wrong branches).

Doing a

   git log --grep='Revert "Merge '

does seem to show that this is a networking pattern. Nasty.

But I hope it also means that you know how to deal with the fallout.

In particular, reverting a merge means that re-doing that merge later
will just be a no-op: the original commits are already merged. You'll
need to revert the revert to get the changes back (or you just need to
re-do the whole thing).

            Linus