From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: licenses <licenses@gentoo.org>
Subject: Re: [gentoo-dev] Re: [RFC] Adding 'GPL-2-only', 'GPL-3-only' etc. license variants for better auditing
Date: Sun, 22 Sep 2019 08:12:32 +0200 [thread overview]
Message-ID: <50df0c8d74f286393362bf5d089706c69f44e63e.camel@gentoo.org> (raw)
In-Reply-To: <20190921224530.GA10927@linux1.home>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Sat, 2019-09-21 at 17:45 -0500, William Hubbs wrote:
> On Sat, Sep 21, 2019 at 09:57:25PM +0200, Michał Górny wrote:
> > On Sat, 2019-09-21 at 14:26 -0500, William Hubbs wrote:
> > > On Sat, Sep 21, 2019 at 09:17:53PM +0200, Ulrich Mueller wrote:
> > > > > > > > > On Sat, 21 Sep 2019, Michał Górny 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+'.
> > > >
> > > > This has been discussed before. There is no such license as GPL-2-only.
> > >
> > > I am with ulm on this one.
> > > We have GPL-2 and GPL-2+ in the tree. The way I read this,
> > > LICENSE="GPL-2" means GPL 2 only and LICENSE="GPL-2+" means GPL-2+.
> > >
> >
> > Have you read my original mail?
>
> Yes, and I just did again, and my position is still the same.
>
I know what we have now and what it means. The mail includes long
explanation why this doesn't work. Repeating what we have now does not
bring any argument to the discussion, except for anger/demotivation
because it feels like you've completely ignored most of the mail
and just reject it on the basis of 'it's not what we have now'.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-09-22 6:12 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
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 [this message]
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=50df0c8d74f286393362bf5d089706c69f44e63e.camel@gentoo.org \
--to=mgorny@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