linux-kernel - Re: [GIT PULL] Kbuild updates for v5.18-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: <CAHk-=wgxcu9DFkXAOAFdDtLWwuv6qb5iV1E69yWE-JEVsd-NFg@mail.gmail.com>
Date:   Tue, 29 Mar 2022 13:10:30 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Masahiro Yamada <masahiroy@...nel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>
Subject: Re: [GIT PULL] Kbuild updates for v5.18-rc1

I pulled this, and then immediately unpulled.

On Mon, Mar 28, 2022 at 5:09 AM Masahiro Yamada <masahiroy@...nel.org> wrote:
>
>  - Change the .config format to use CONFIG_FOO=n instead of
>    "# CONFIG_FOO is not set"

This is unacceptable.

The change was apparently made to make automation easier, at the
expense of making it harder for people to parse.

That is not a valid tradeoff.

I _look_ at my config files. Constantly. I don't want some mess where
it's really damn hard to visually tell the difference between "this is
enabled" and "this is not enabled".

So no, I'm not pulling this kind of horrible "make it simpler for
automation, and harder for humans" to read.

                Linus