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] [day] [month] [year] [list]
Message-ID: <3236c17c-2861-478d-b094-0944afba4874@gmail.com>
Date: Sat, 21 Jun 2025 12:43:02 +0200
From: Xose Vazquez Perez <xose.vazquez@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
 LINUX SPDX ML <linux-spdx@...r.kernel.org>,
 LINUX KERNEL ML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] LICENSES: refresh FSF GFDL/GPL licences

On 6/21/25 9:20 AM, Greg Kroah-Hartman wrote:

> You also changed whitespace and some terms, and did not describe that
> here, why?
> 
> This license text comes from the SPDX repo, why not use that instead?
> 
> Or better yet, _JUST_ change the address, if that is correct with what
> the FSF has published, and that's it.  Unneeded whitespace issues are
> not a good idea and not needed at all.
 >
 > Please don't reformat everything for no good reason.  Let's stick with
 > what spdx has as that is what everyone has agreed on.


I did not touch a single byte of the original gnu.org licences.

Just deleted the text of the licence from the Linux file, wget it from gnu.org,
cat to the file, and did the patch. Plain and simple.

If there are any inconsistencies, they were already present in the Linux files,
and/or spdx.org.

I do not like to change any part of legal texts from the original source.
Even control character cleanups (^L, ^M, TAB, ...).

Thanks for your time, but I am not going to do it.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ