From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] dosfstools: update native to 2.11
Date: Fri, 09 Dec 2011 11:21:04 -0800 [thread overview]
Message-ID: <4EE25FA0.2050500@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKpr=xgxfJcrzsbv8q+VQh8oQOdKjQurev7hVjiMAv1PkA@mail.gmail.com>
On 12/09/2011 11:17 AM, Otavio Salvador wrote:
> On Fri, Dec 9, 2011 at 17:15, Darren Hart <dvhart@linux.intel.com
> <mailto:dvhart@linux.intel.com>> wrote:
>
> What are these licensing issues, and are they no longer an issue?
>
>
> Newer dosfstools is GPLv3.
So pulling this in would mean we can't build live images when building
non GPLv3 images? We are looking to revamp the image creation, but until
then I can't agree to this.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-12-09 19:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 15:40 [PATCH 0/3] Misc fixes/improvements Otavio Salvador
2011-12-08 15:40 ` [PATCH 1/3] cross.bbclass: add virtclass handler Otavio Salvador
2011-12-08 22:09 ` Richard Purdie
2012-02-07 19:28 ` Otavio Salvador
2011-12-08 15:40 ` [PATCH 2/3] dosfstools: update native to 2.11 Otavio Salvador
2011-12-09 19:08 ` Kamble, Nitin A
2011-12-09 19:15 ` Darren Hart
2011-12-09 19:17 ` Otavio Salvador
2011-12-09 19:21 ` Darren Hart [this message]
2011-12-09 19:35 ` Otavio Salvador
2011-12-09 19:42 ` Darren Hart
2011-12-12 23:15 ` Saul Wold
2011-12-13 15:49 ` Richard Purdie
2011-12-08 15:40 ` [PATCH 3/3] scripts/send-pull-request: allow sending of patches without a cover letter Otavio Salvador
2011-12-09 19:18 ` Darren Hart
2011-12-10 0:07 ` Richard Purdie
2011-12-10 15:51 ` Otavio Salvador
2011-12-09 19:34 ` Khem Raj
2011-12-09 19:36 ` Otavio Salvador
2011-12-09 19:45 ` Darren Hart
2011-12-09 19:48 ` 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=4EE25FA0.2050500@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@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