linux-kernel - Re: [PATCH 1/9] CodingStyle: make Documentation/CodingStyle into symlink

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: <20250513195016.GI2023217@ZenIV>
Date: Tue, 13 May 2025 20:50:16 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Alexey Dobriyan <adobriyan@...il.com>
Cc: Jonathan Corbet <corbet@....net>, workflows@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/9] CodingStyle: make Documentation/CodingStyle into
 symlink

On Tue, May 13, 2025 at 10:26:12PM +0300, Alexey Dobriyan wrote:

> Right now it is clear that Greg objects but I personally think
> his counter-argument is weak.
> 
> He is basically saying that LOC count is too much so Linux should stick
> to how things were always have been even if "old style" is objectively
> inferior.

Objectively by which metrics?  You are trying to force your personal
preferences upon everybody else, doing that on a list most of us
are not even subscribed to.

You are trying to change an equivalent of build artifact, without
bothering to change the source it is derived from.  That file is
*not* a mechanism for changing reality; it codifies the existing
general agreement between the states of wetware in developers.
And if you are interested in changing these states of wetware,
l-k is the wrong place for that.