From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 1/4] lvm2: remove unbuildable 2.02.138
Date: Thu, 09 Feb 2017 18:11:58 +0100 [thread overview]
Message-ID: <1486660318.13854.105.camel@intel.com> (raw)
In-Reply-To: <CAMKF1spq2eiKHXrz19ZzRWmwzWUKsSSHbunLfqRND98SjkHgVg@mail.gmail.com>
On Wed, 2017-02-08 at 20:21 +0000, Khem Raj wrote:
> Can you check if this is the last gpl2 version
According to the recipe, both 2.02.138 and 2.02.166 are under LICENSE =
"GPLv2 & LGPLv2", and that also seems to be what the current code is
licensed under: https://git.fedorahosted.org/cgit/lvm2.git/tree/
So GPLv2 vs. GPLv3 wasn't the reason for keeping the old version.
BTW, do all mails from openembedded-devel have Reply-To:
<openembedded-devel@lists.openembedded.org> set? openembedded-core
doesn't seem to have that.
I have a mail filter in place which will bring personal replies to my
attention sooner, but Reply-To to the list defeats that.
--
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-02-09 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 9:37 [meta-oe][PATCH 0/4] native cryptsetup and fuse Patrick Ohly
2017-02-08 9:37 ` [meta-oe][PATCH 1/4] lvm2: remove unbuildable 2.02.138 Patrick Ohly
2017-02-08 20:21 ` Khem Raj
2017-02-09 17:11 ` Patrick Ohly [this message]
2017-02-09 17:17 ` Khem Raj
2017-02-09 19:21 ` Reply-To (was: Re: [meta-oe][PATCH 1/4] lvm2: remove unbuildable 2.02.138) Patrick Ohly
2017-02-10 23:15 ` [meta-oe][PATCH 1/4] lvm2: remove unbuildable 2.02.138 Martin Jansa
2017-02-13 7:23 ` Patrick Ohly
2017-02-08 9:37 ` [meta-oe][PATCH 2/4] fuse: support native compilation Patrick Ohly
2017-02-08 9:37 ` [meta-oe][PATCH 3/4] lvm2: enable " Patrick Ohly
2017-02-08 9:37 ` [meta-oe][PATCH 4/4] cryptsetup: " Patrick Ohly
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=1486660318.13854.105.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-devel@lists.openembedded.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