linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allison Randal <allison@lohutok.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-spdx@vger.kernel.org
Subject: Re: clarification on -only and -or-later
Date: Wed, 22 May 2019 10:22:49 -0400	[thread overview]
Message-ID: <fdd995ec-4ae5-ac8f-4fe2-598c89c728a3@lohutok.net> (raw)
In-Reply-To: <20190522140014.GA8996@kroah.com>

On 5/22/19 3:00 PM, Greg KH wrote:
> 
> But note, we have already marked such files as "GPL-1.0+" in the past,
> so any change in that behavior would require us go back and change what
> we did, showing the justification for that.
> 
> I would stick to the rule of what we have already done in these cases,
> it's simpler and seems to make sense of a crazy situation.

Fair. If we have a precedent of keeping GPL-1.0 in the SPDX license
notices, then we should be consistent and follow that rule in this
cleanup process.

Allison

  parent reply	other threads:[~2019-05-22 14:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 18:40 clarification on -only and -or-later J Lovejoy
2019-05-20 18:52 ` Greg KH
2019-05-20 19:26   ` J Lovejoy
2019-05-20 21:35     ` Allison Randal
2019-05-20 22:09       ` J Lovejoy
2019-05-20 22:19         ` Allison Randal
2019-05-20 22:52           ` J Lovejoy
2019-05-20 23:15             ` Allison Randal
2019-05-21 17:24 ` Bradley M. Kuhn
2019-05-21 18:05   ` J Lovejoy
2019-05-22 13:23     ` Greg KH
2019-05-22 13:53       ` Allison Randal
2019-05-22 14:00         ` Greg KH
2019-05-22 14:20           ` Thomas Gleixner
2019-05-22 14:30             ` Allison Randal
2019-05-22 15:45               ` Greg KH
2019-05-22 19:04                 ` Bradley M. Kuhn
2019-05-22 14:22           ` Allison Randal [this message]
2019-05-22 15:03           ` J Lovejoy
     [not found]   ` <5EB6B416-F24C-4741-BC0E-6C1896E7A705@jilayne.com>
2019-05-21 21:14     ` 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=fdd995ec-4ae5-ac8f-4fe2-598c89c728a3@lohutok.net \
    --to=allison@lohutok.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-spdx@vger.kernel.org \
    /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).