From: Mark Hatle <mark.hatle@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4]Add FUSE: File system in Userspace
Date: Thu, 30 May 2013 11:59:37 -0500 [thread overview]
Message-ID: <51A78579.3050704@windriver.com> (raw)
In-Reply-To: <BD275838-4C3A-49B8-8CEF-27A3A7BBC81E@gmail.com>
On 5/30/13 11:56 AM, Khem Raj wrote:
>
> On May 30, 2013, at 8:49 AM, Mark Hatle <mark.hatle@windriver.com> wrote:
>
>> The issue isn't that it's a few bad recipes, the issue is that meta-oe is a collection of software that doesn't fit anywhere else. (I'm speaking specifically of meta-oe, -not- meta-openembedded which has multiple layers in it.)
>
> OK I see that you are not supporting meta-oe in your commercial product but are in need of bits and pieces from it I would suggest to poach the recipes and keep them in your own supported layer if you do not wish to support meta-oe and It would be nice if you fed back any bug fixes or changes.
>
Just to be clear, this is exactly what we are doing, and intend to do. Pick
pieces as needed from meta-oe, submit fixes/uprevs back to meta-oe for those pieces.
If we see a more general need we will submit them to oe-core as well, if they're
not accepted, then they go back to meta-oe.
--Mark
prev parent reply other threads:[~2013-05-30 16:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 9:01 [PATCH 0/4]Add FUSE: File system in Userspace Hongxu Jia
2013-05-30 9:01 ` [PATCH 1/4] fuse: import recipe from meta-oe Hongxu Jia
2013-05-30 9:01 ` [PATCH 2/4] ntfs-3g-ntfsprogs:import and update " Hongxu Jia
2013-05-30 9:01 ` [PATCH 3/4] fuse-exfat: add version 1.0.1 Hongxu Jia
2013-05-30 9:01 ` [PATCH 4/4] exfat-utils: " Hongxu Jia
2013-05-30 9:18 ` [PATCH 0/4]Add FUSE: File system in Userspace Jack Mitchell
2013-05-30 10:38 ` Paul Eggleton
2013-05-30 12:17 ` Mark Hatle
2013-05-30 12:58 ` Philip Balister
2013-05-30 15:49 ` Mark Hatle
2013-05-30 16:13 ` Phil Blundell
2013-05-30 16:18 ` Mark Hatle
2013-06-03 11:20 ` Philip Balister
2013-06-03 14:22 ` Mark Hatle
2013-05-30 16:56 ` Khem Raj
2013-05-30 16:59 ` Mark Hatle [this message]
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=51A78579.3050704@windriver.com \
--to=mark.hatle@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox