linux-kernel - Re: [GIT PULL] cgroup changes for v5.19-rc1

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: <Yo6HMpEodz36o4Dc@slm.duckdns.org>
Date:   Wed, 25 May 2022 09:44:50 -1000
From:   Tejun Heo <tj@...nel.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Cgroups <cgroups@...r.kernel.org>
Subject: Re: [GIT PULL] cgroup changes for v5.19-rc1

On Wed, May 25, 2022 at 12:43:09PM -0700, Linus Torvalds wrote:
> On Mon, May 23, 2022 at 4:44 PM Tejun Heo <tj@...nel.org> wrote:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.19
> 
> Your two pulls sadly broke the perfect signed tag streak that we had
> this merge window up until just now.
> 
> I'm very happy to see how people have started doing signed tags for
> everything, but that only makes your pull requests stand out even
> more.
> 
> So yeah, despite not requiring it for kernel.org pulls, I'd _really_
> like to make using signed tags just be the standard behavior for all
> the kernel pull requests.
> 
> Can we try to aim for that next time? Please?

Hahaha, yeah, I lost my private key many years ago, so gotta get that sorted
out first. Will do the signed pull from now on.

Thanks.

-- 
tejun