From: Ulf Samuelsson <ulf@emagii.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Use GFDL-1.1 instead of GFDLv1.1
Date: Wed, 30 Sep 2015 13:53:08 +0200 [thread overview]
Message-ID: <560BCD24.7090403@emagii.com> (raw)
In-Reply-To: <3684850.Dr1EhiOegx@peggleto-mobl.ger.corp.intel.com>
There is no GFDLv1.1 file in the license directory
----------------------------------------------------------------------------------
openembedded-core/meta/files/common-licenses$ ls GFDL*
GFDL-1.1 GFDL-1.2 GFDL-1.3
----------------------------------------------------------------------------------
It does not make sense to have a duplicate file.
Incidently, the GFDL-1.1 file contains the GFDL-1.2 license, not the 1.1
license.
/Ulf
Den 2015-09-30 kl. 13:05, skrev Paul Eggleton:
> On Wednesday 30 September 2015 03:10:56 Khem Raj wrote:
>> On Wed, Sep 30, 2015 at 1:26 AM, Ulf Samuelsson <ulf@emagii.com> wrote:
>>> -LICENSE = "GPLv2 & LGPLv2 & GFDLv1.1"
>>> +LICENSE = "GPLv2 & LGPLv2 & GFDL-1.1"
>> IIRC both are correct
> I don't think we have an SPDXLICENSEMAP entry for this though, so it won't be
> being mapped (unlike GPLv2 -> GPL-2.0).
>
> Cheers,
> Paul
>
next prev parent reply other threads:[~2015-09-30 11:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 8:26 [meta-gnome][dizzy][PATCH] Use GFDL-1.1 instead of GFDLv1.1 Ulf Samuelsson
2015-09-30 8:26 ` [PATCH] " Ulf Samuelsson
2015-09-30 10:10 ` Khem Raj
2015-09-30 11:05 ` Paul Eggleton
2015-09-30 11:53 ` Ulf Samuelsson [this message]
2015-09-30 11:58 ` Paul Eggleton
2015-09-30 22:08 ` Ulf Samuelsson
2015-10-01 6:54 ` Paul Eggleton
2015-10-01 7:44 ` Martin Jansa
2015-09-30 15:05 ` Khem Raj
2015-09-30 8:26 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2015-10-01 7:55 [meta-gnome][dizzy][PATCH] gnome-panel*: " Ulf Samuelsson
2015-10-01 7:55 ` [PATCH] " Ulf Samuelsson
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=560BCD24.7090403@emagii.com \
--to=ulf@emagii.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=raj.khem@gmail.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 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.