linux-kernel - Re: [GIT PULL] perf tools fixes for v5.11, 2nd batch

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, 22 Jan 2021 13:59:02 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:     Ingo Molnar <mingo@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Jiri Olsa <jolsa@...nel.org>,
        Namhyung Kim <namhyung@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-perf-users@...r.kernel.org,
        Adrian Hunter <adrian.hunter@...el.com>,
        Jin Yao <yao.jin@...ux.intel.com>,
        Joakim Zhang <qiangqing.zhang@....com>,
        John Garry <john.garry@...wei.com>,
        Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [GIT PULL] perf tools fixes for v5.11, 2nd batch

On Fri, Jan 22, 2021 at 5:52 AM Arnaldo Carvalho de Melo
<acme@...nel.org> wrote:
>
> Test results in the signed tag at:

Side note: I'd actually prefer if you didn't do this. These big things
end up being (a hidden) part of the merge commit (and that's how the
tag verification works after-the-fact: ie I don't just verify the tag
when I pull, you can also do the verification later), and it really
makes zero sense to add 28kB of data to each merge just because you
hid them in the signed tag.

It would actually be better to have it just in the email at the end,
not in the tag.

Please?

              Linus