All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adrian Bunk" <bunk@stusta.de>
To: matthias.schoepfer@googlemail.com
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org,
	Matthias Schoepfer <matthias.schoepfer@ithinx.io>
Subject: Re: [OE-core] [meta-oe][PATCH 3/4] libgcrypt: made libgcrypt-lic license "GPLv2+ & LGPLv2.1+"
Date: Tue, 26 May 2020 14:37:29 +0300	[thread overview]
Message-ID: <20200526113729.GA26509@localhost> (raw)
In-Reply-To: <b595d584-b544-b755-d175-85fffbfd31e5@googlemail.com>

On Tue, May 26, 2020 at 01:20:50PM +0200, Matthias Schoepfer via lists.openembedded.org wrote:
>...
> The question here seems to be, is the GPLv3 License itself GPLv3 licensed.
>...

  Everyone is permitted to copy and distribute verbatim copies
  of this license document, but changing it is not allowed.


cu
Adrian

  reply	other threads:[~2020-05-26 11:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  8:12 [meta-oe][PATCH 1/4] libgcc: made libgcc-lic "GPL-3.0-with-GCC-exception" Matthias Schoepfer
2020-05-26  8:12 ` [meta-oe][PATCH 2/4] elfutils: made elfutils-lic "GPLv2 | LGPLv3+" Matthias Schoepfer
2020-05-26  8:12 ` [meta-oe][PATCH 3/4] libgcrypt: made libgcrypt-lic license "GPLv2+ & LGPLv2.1+" Matthias Schoepfer
2020-05-26  8:19   ` [OE-core] " Richard Purdie
2020-05-26 11:20     ` Matthias Schoepfer
2020-05-26 11:37       ` Adrian Bunk [this message]
2020-05-26 11:37       ` Richard Purdie
2020-07-06 16:16         ` Matthias Schoepfer
2020-07-06 16:26           ` Richard Purdie
2020-07-08  8:19             ` Matthias Schoepfer
2020-07-08  9:00               ` Richard Purdie
2020-05-26  8:12 ` [meta-oe][PATCH 4/4] libksba: made libksba-lic "GPLv2+ | LGPLv3+" Matthias Schoepfer

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=20200526113729.GA26509@localhost \
    --to=bunk@stusta.de \
    --cc=matthias.schoepfer@googlemail.com \
    --cc=matthias.schoepfer@ithinx.io \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.