From: Patrick Ohly <patrick.ohly@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 2/2] autoconf-archive: simplify and fix recipe
Date: Fri, 28 Jul 2017 20:43:09 +0200 [thread overview]
Message-ID: <1501267389.18875.14.camel@intel.com> (raw)
In-Reply-To: <CAMKF1sq12PyVfGStOaeuSBHx0c96chYuD7jM27pfpcm9zNurhg@mail.gmail.com>
On Fri, 2017-07-28 at 09:44 -0700, Khem Raj wrote:
> On Fri, Jul 28, 2017 at 7:49 AM, Patrick Ohly <patrick.ohly@intel.com
> > +LICENSE = "GPLv3"
>
> Perhaps GPL-3.0-with-autoconf-exception would be more accurate here.
I wasn't sure whether such a thing existed already, but yes, as it does
it could be used here, with COPYING.EXCEPTION added as second
LIC_FILES_CHKSUM entry. I didn't want to be that fancy, but I can also
do a v3 with that change.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-07-28 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 14:49 [PATCH v2 0/2] move autoconf-archive into OE-core Patrick Ohly
2017-07-28 14:49 ` [PATCH v2 1/2] autoconf-archive: move from meta-oe to OE-core Patrick Ohly
2017-07-28 14:49 ` [PATCH v2 2/2] autoconf-archive: simplify and fix recipe Patrick Ohly
2017-07-28 16:44 ` Khem Raj
2017-07-28 18:43 ` Patrick Ohly [this message]
2017-07-28 18:45 ` Khem Raj
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=1501267389.18875.14.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--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.