From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Chris Verges <kg4ysn@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: bbappend
Date: Tue, 12 Jul 2011 15:56:12 +0100 [thread overview]
Message-ID: <201107121556.12195.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <20110712143101.GA2392@cverges-dev-lnx>
On Tuesday 12 July 2011 15:31:01 you wrote:
> On Tue, Jul 12, 2011 at 03:18:50PM +0100, Paul Eggleton wrote:
> > Possibly, however as a general suggestion I would recommend moving
> > things over to being based on oe-core if at all possible. I realise
> > this is not going to be practical for everyone in the short term,
> > however OE classic will stop being maintained at some point in the
> > near future, so the sooner you move the better - plus you get to take
> > advantage of the additional features and cleanups in oe-core as well.
>
> I'd love to. My most recent project is just starting out, so it's a
> good time to make the switch. Are there any good references for
> performing a migration?
We're rather lacking in oe-core specific documentation right now; however, you
should be able to just grab oe-core and get started with it fairly easily:
https://wiki.yoctoproject.org/wiki/OpenEmbedded-Core
If you have any questions feel free to post them on the oe-core list:
http://lists.linuxtogo.org/mailman/listinfo/openembedded-core
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-07-12 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E1C0C99.3040508@nedap.com>
2011-07-12 8:58 ` bbappend Jaap de Jong
2011-07-12 9:42 ` bbappend Paul Eggleton
2011-07-12 14:08 ` bbappend Chris Verges
2011-07-12 14:18 ` bbappend Paul Eggleton
2011-07-12 14:31 ` bbappend Chris Verges
2011-07-12 14:56 ` Paul Eggleton [this message]
2011-09-30 6:03 bbappend Jaap de Jong
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=201107121556.12195.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=kg4ysn@gmail.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