From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: fuse update
Date: Mon, 09 May 2011 09:46:35 -0700 [thread overview]
Message-ID: <4DC81A6B.3040708@linux.intel.com> (raw)
In-Reply-To: <BANLkTinK3Cqk=JxH-TH=xM395JUXN5rfTg@mail.gmail.com>
On 05/03/2011 07:06 AM, Otavio Salvador wrote:
> Hello,
>
> I am migrating some stuff to oe-core and found it has fuse at
> meta-demoapps. It seems no recipes depends on fuse in oe-core and thus
> I am wondering how is better to deal with its updating as:
>
> - should it be done in oe-core?
> - should it be moved to meta-oe?
>
> The requirement for me to update it is due it being required by a new
> recipe I am adding to meta-oe and then it seems more logical to me to
> move fuse to meta-oe but I am curious to hear from others about it.
>
It would make sense for you to move it to meta-oe at this time, if we
find more recipes require it our other layers are needed it, then we can
consider it for oe-core.
Sau!
> Cheers,
>
next prev parent reply other threads:[~2011-05-09 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 14:06 fuse update Otavio Salvador
2011-05-09 16:46 ` Saul Wold [this message]
2011-05-09 17:50 ` Otavio Salvador
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=4DC81A6B.3040708@linux.intel.com \
--to=sgw@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