linux-kernel - Re: [GIT PULL] process fixes for v5.4-rc2

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-=wgNpZdAy3G+6zekugbV+SObfPQRy=fneqwPomFRX3Ym+A@mail.gmail.com>
Date:   Fri, 4 Oct 2019 10:24:05 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Christian Brauner <christian.brauner@...ntu.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] process fixes for v5.4-rc2

On Fri, Oct 4, 2019 at 2:40 AM Christian Brauner
<christian.brauner@...ntu.com> wrote:
>
> This pull request contains a couple of fixes:

Pulled.

Small note: it is sad, and I'm ashamed of my life, but to me "process"
these days is about development process rather than about a group of
threads sharing a VM.

I know, I know. I feel like a (shudder) manager. But when I see a pull
request for "process fixes", my mind goes to documentation about our
processes for pull requests and sending patches etc.

You don't need to change anything in your life or emails - you've got
it right - but this just explains why your pull request is now labeled
"clone3/pidfd fixes" in my tree, and why it might be better to talk to
me about "treads" rather than processes.

             Linus