From: Thomas Gleixner <tglx@linutronix.de>
To: Richard Fontana <rfontana@redhat.com>
Cc: linux-spdx@vger.kernel.org
Subject: Re: [Batch 1 - patch 12/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_208.RULE
Date: Mon, 06 Jun 2022 22:17:46 +0200 [thread overview]
Message-ID: <87bkv55yxh.ffs@tglx> (raw)
In-Reply-To: <CAC1cPGzeXeGDKtGPED1tMX1WybjRrxypfw5+SPs_kXwdO7NWiA@mail.gmail.com>
On Mon, Jun 06 2022 at 16:11, Richard Fontana wrote:
> On Mon, Jun 6, 2022 at 3:58 PM Thomas Gleixner <tglx@linutronix.de> wrote:
>> Based on the normalized pattern:
>>
>> this program is free software you can redistribute it and/or modify it
>> under the terms of version 2 of the gnu general public license as
>> published by the free software foundation this program is distributed
>> in the hope that it will be useful all express or implied conditions
>> representations and warranties including any implied warranty of
>> merchantability fitness for a particular purpose or non-infringement
>> are disclaimed except to the extent that such disclaimers are held to
>> be legally invalid see the gnu general public license for more details
>> a copy of which can be found in the file copying included with this
>> package
>
> I forget how we dealt with things like this in the initial large batch
> some years ago but I remember raising the concern that some bespoke
> license notices contained disclaimer language that was arguably
> materially different in some way from what is found in GPLv2 itself.
> This might be another example. I think in some such cases we at least
> considered preserving the nonstandard disclaimer language.
IIRC, there was no real conclusion aside of dealing with this later :)
One way would be to talk to the original author (if still reachable) and
ask for clarification/permission to remove it. In this case Broadcom.
Thanks,
tglx
next prev parent reply other threads:[~2022-06-06 20:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 19:58 [Batch 1 - patch 12/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_208.RULE Thomas Gleixner
2019-05-21 17:58 ` Meta-question on GPL compliance of this activity Richard Fontana
2019-05-21 18:59 ` J Lovejoy
2019-05-21 21:08 ` Bradley M. Kuhn
2019-05-22 9:40 ` Thomas Gleixner
2019-05-22 13:30 ` Greg KH
2019-05-23 4:41 ` Bradley M. Kuhn
2019-05-23 5:42 ` Thomas Gleixner
2019-05-22 16:14 ` J Lovejoy
2019-05-22 21:10 ` John Sullivan
2019-05-23 1:19 ` J Lovejoy
2019-05-23 6:06 ` Thomas Gleixner
2019-05-29 20:57 ` John Sullivan
2019-05-29 21:30 ` Greg KH
2019-06-01 3:22 ` John Sullivan
2019-06-01 9:31 ` Greg KH
2019-06-01 4:21 ` Richard Fontana
2019-05-24 4:33 ` Richard Fontana
2019-05-24 5:20 ` Greg KH
2019-05-24 20:24 ` Allison Randal
2019-05-25 1:07 ` Richard Fontana
2019-05-27 21:23 ` Allison Randal
2019-05-25 16:56 ` Greg KH
2019-05-27 21:54 ` Allison Randal
2019-05-28 7:21 ` Dominik Brodowski
2019-05-22 13:27 ` Greg KH
2019-05-22 14:16 ` Thomas Gleixner
2019-05-22 16:33 ` J Lovejoy
2019-05-22 16:52 ` Thomas Gleixner
2019-05-22 17:00 ` J Lovejoy
2022-06-06 20:11 ` [Batch 1 - patch 12/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_208.RULE Richard Fontana
2022-06-06 20:17 ` Thomas Gleixner [this message]
2022-06-07 18:12 ` Bradley M. Kuhn
2022-06-07 23:05 ` Thomas Gleixner
2022-06-08 8:33 ` Allison Randal
2022-06-08 14:04 ` Bradley M. Kuhn
2022-06-08 14:59 ` Allison Randal
2022-06-08 17:18 ` Bradley M. Kuhn
2022-06-08 18:54 ` Richard Fontana
2022-06-08 19:29 ` Bradley M. Kuhn
[not found] ` <02f4021f-63a5-4796-d790-2bacd37b90d2@jilayne.com>
2022-06-09 0:31 ` Bradley M. Kuhn
2022-06-09 4:51 ` J Lovejoy
2022-06-09 15:03 ` Bradley M. Kuhn
2022-06-09 2:35 ` Richard Fontana
2022-06-06 20:31 ` Bradley M. Kuhn
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=87bkv55yxh.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-spdx@vger.kernel.org \
--cc=rfontana@redhat.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