public inbox for linux-spdx@vger.kernel.org
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LINUX SPDX ML <linux-spdx@vger.kernel.org>,
	LINUX KERNEL ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] LICENSES: refresh FSF GFDL/GPL licences
Date: Sat, 21 Jun 2025 12:43:02 +0200	[thread overview]
Message-ID: <3236c17c-2861-478d-b094-0944afba4874@gmail.com> (raw)
In-Reply-To: <2025062111-detonate-clapped-b630@gregkh>

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.

      reply	other threads:[~2025-06-21 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-21  1:21 [PATCH 1/2] LICENSES: refresh FSF GFDL/GPL licences Xose Vazquez Perez
2025-06-21  1:21 ` [PATCH 2/2] LICENSES: refresh FSF LGPL licences Xose Vazquez Perez
2025-06-21  7:21   ` Greg Kroah-Hartman
2025-06-21  7:20 ` [PATCH 1/2] LICENSES: refresh FSF GFDL/GPL licences Greg Kroah-Hartman
2025-06-21 10:43   ` Xose Vazquez Perez [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3236c17c-2861-478d-b094-0944afba4874@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox