From: Matt Turner <mattst88@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Cc: licenses <licenses@gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Adding 'GPL-2-only', 'GPL-3-only' etc. license variants for better auditing
Date: Sat, 21 Sep 2019 16:21:21 -0700 [thread overview]
Message-ID: <CAEdQ38F+K2QPHz1A-Rq21X4BQBVx2TrYGryA8A5A=SF44mq-xA@mail.gmail.com> (raw)
In-Reply-To: <CAEdQ38Gq=w170zDT11Ys7BC_kxK1AmGni-sixaTq-0k88Ejy+w@mail.gmail.com>
On Sat, Sep 21, 2019 at 9:57 AM Matt Turner <mattst88@gentoo.org> wrote:
>
> On Sat, Sep 21, 2019 at 9:09 AM Michał Górny <mgorny@gentoo.org> wrote:
> > TL;DR: I'd like to replace 'GPL-2' with 'GPL-2-only' etc., having
> > the former trigger QA warning asking the dev to double-check if it's
> > 'GPL-2-only' or 'GPL-2+'.
>
> I think that's a good idea.
An idea to consider: use SPDX license identifiers (see
https://spdx.org/licenses/)
For GPL 2 they are "GPL-2.0-only" and "GPL-2.0-or-later"
next prev parent reply other threads:[~2019-09-21 23:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 16:09 [gentoo-dev] [RFC] Adding 'GPL-2-only', 'GPL-3-only' etc. license variants for better auditing Michał Górny
2019-09-21 16:57 ` Matt Turner
2019-09-21 23:21 ` Matt Turner [this message]
2019-09-21 23:46 ` Ulrich Mueller
2019-09-22 0:03 ` Matt Turner
2019-09-24 3:45 ` Matt Turner
2019-09-24 7:13 ` Ulrich Mueller
2019-09-24 15:39 ` Matt Turner
2019-09-21 19:17 ` [gentoo-dev] " Ulrich Mueller
2019-09-21 19:26 ` William Hubbs
2019-09-21 19:57 ` Michał Górny
2019-09-21 22:45 ` William Hubbs
2019-09-22 6:12 ` Michał Górny
2019-09-24 1:42 ` Jason Zaman
2019-09-24 3:43 ` Matt Turner
2019-09-24 6:16 ` Ulrich Mueller
2019-09-21 19:56 ` [gentoo-dev] " Michael Orlitzky
2019-09-21 19:59 ` Michał Górny
2019-09-21 20:02 ` Michael Orlitzky
2019-09-21 20:58 ` [gentoo-dev] " Ulrich Mueller
2019-09-21 22:01 ` Matt Turner
2019-09-21 23:38 ` Ulrich Mueller
2019-09-22 9:16 ` Kent Fredric
2019-09-22 16:36 ` [gentoo-dev] " Richard Yao
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='CAEdQ38F+K2QPHz1A-Rq21X4BQBVx2TrYGryA8A5A=SF44mq-xA@mail.gmail.com' \
--to=mattst88@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=licenses@gentoo.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