linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
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 2/2] LICENSES: refresh FSF LGPL licences
Date: Sat, 21 Jun 2025 09:21:28 +0200	[thread overview]
Message-ID: <2025062157-framing-designed-76cd@gregkh> (raw)
In-Reply-To: <20250621012117.91729-2-xose.vazquez@gmail.com>

On Sat, Jun 21, 2025 at 03:21:14AM +0200, Xose Vazquez Perez wrote:
> Old licences have been modified, because FSF postal address was changed:
> https://lists.gnu.org/archive/html/info-gnu/2024-09/msg00000.html
> https://www.fsf.org/blogs/community/fsf-office-closing-party
> https://www.fsf.org/about/contact/mailing
> 
> Just "cut and paste" from original sources:
> https://www.gnu.org/licenses/old-licenses/lgpl-2.0.txt
> https://www.gnu.org/licenses/old-licenses/lgpl-2.1.txt
> 
> Relevant change: postal address was replaced with an URL.
> 
> There are many changes, because the original text from
> spdx.org is a bit odd. Maybe an old copy :-?

Please don't reformat everything for no good reason.  Let's stick with
what spdx has as that is what everyone has agreed on.

thanks,

greg k-h

  reply	other threads:[~2025-06-21  7:21 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 [this message]
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

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=2025062157-framing-designed-76cd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=xose.vazquez@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).