linux-kernel - Re: [GIT PULL] tracing: Fix to recursion protection for 5.15

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:   Wed, 20 Oct 2021 23:16:36 -0700
From:   Joe Perches <joe@...ches.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Steven Rostedt <rostedt@...dmis.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Petr Mladek <pmladek@...e.com>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [GIT PULL] tracing: Fix to recursion protection for 5.15

On Wed, 2021-10-20 at 20:08 -1000, Linus Torvalds wrote:
> it's probably better to have too many cc's listed in the commit
> than too few - at least within reason.
> 
> Because if a commit turns out to cause problems, the list of email
> addresses mentioned in the commit message should be seen as the
> primary list of "hey people, this patch you were involved with has
> issues"

IMO: cc's aren't all that valuable as part of a commit message.

Generally, a tool like b4 should be able to create a list of any
email addresses in a thread linked commit.