Re: [PATCH 1/2] LICENSES: refresh FSF GFDL/GPL licences

2025-06-21 Thread Xose Vazquez Perez

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.



Re: [PATCH 1/2] LICENSES: refresh FSF GFDL/GPL licences

2025-06-21 Thread Greg Kroah-Hartman
On Sat, Jun 21, 2025 at 03:21:13AM +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/msg0.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/fdl-1.1.txt
> https://www.gnu.org/licenses/old-licenses/fdl-1.2.txt
> https://www.gnu.org/licenses/old-licenses/gpl-1.0.txt
> https://www.gnu.org/licenses/old-licenses/gpl-2.0.txt
> 
> Relevant change: postal address was replaced with an URL.

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.

thanks,

greg k-h