linux-kernel - Re: [GIT PULL REQUEST] watchdog

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: <CAHk-=wi7NEnwnbrNewJLvjsMc4gAOmGb4nOMfooZUXMr627Zxg@mail.gmail.com>
Date:   Tue, 7 Sep 2021 13:58:38 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Wim Van Sebroeck <wim@...ux-watchdog.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux Watchdog Mailing List <linux-watchdog@...r.kernel.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Christine Zhu <Christine.Zhu@...iatek.com>,
        Curtis Klein <curtis.klein@....com>,
        Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org>,
        Jan Kiszka <jan.kiszka@...mens.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
        Rikard Falkeborn <rikard.falkeborn@...il.com>,
        Sam Shih <sam.shih@...iatek.com>,
        Stefan Wahren <stefan.wahren@...e.com>
Subject: Re: [GIT PULL REQUEST] watchdog - v5.12 Merge window

On Tue, Sep 7, 2021 at 1:46 PM Wim Van Sebroeck <wim@...ux-watchdog.org> wrote:
>
> My Apologies. The subject of this e-mail is wrong again. It should have been [GIT PULL REQUEST] watchdog - v5.15 Merge window

Heh. That was fairly obvious. No problem.

My email search terms end up being just "git" and "pull", so it's not
like I end up even really looking at the version numbers except closer
to the end of the release. At that point people start sending me early
pull requests for the next merge window, and I start looking more
closely just to make sure I differentiate between "fixes for this
release" and "updates for the next merge window".

... and even then, it's usually pretty obvious from the actual
contents, and if somebody gets a version number wrong it generally
isn't all that confusing.

            Linus