From: Denis 'GNUtoo' Carikli <gnutoo@no-log.org>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: OE-Classic recipe migration status
Date: Mon, 19 Nov 2012 14:57:28 +0100 [thread overview]
Message-ID: <20121119145728.32c62e6c@gnutoo-desktop> (raw)
In-Reply-To: <20121112182616.GB22235@novatech.datenfreihafen.org>
On Mon, 12 Nov 2012 18:26:16 +0000
Stefan Schmidt <stefan@datenfreihafen.org> wrote:
> I now longer work for BugLabs but during my last months there I split
> up our bunch of recipes according to what we think was sane at that
> time. Think end of last year here.
>
> The BSP layer can be found here:
> https://github.com/buglabs/meta-bug
However (since my last pull request) it fails to boot and blocks in
systemd with an angstrom image, I'll get the diff and a log soon.
> And BugLabs specific recipes here:
> https://github.com/buglabs/meta-buglabs
Nice, I didn't know about it.
PS: Note that I don't work for Buglabs either, I just happen to have
some buglabs(bug 2.0, bug 1.3 wifi, bug 1.3 + many modules) devices.
Denis.
next prev parent reply other threads:[~2012-11-19 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 19:11 OE-Classic recipe migration status Paul Eggleton
2012-11-11 19:52 ` Martin Jansa
2012-11-11 19:58 ` Paul Eggleton
[not found] ` <20121111201613.GB3407@jama.jama.net>
2012-11-11 20:49 ` Paul Eggleton
2012-11-11 23:24 ` [oe] " Otavio Salvador
2012-11-12 8:54 ` Paul Eggleton
2012-11-12 18:26 ` Stefan Schmidt
2012-11-19 13:57 ` Denis 'GNUtoo' Carikli [this message]
2012-11-12 22:10 ` Phil Blundell
2012-11-13 10:42 ` Paul Eggleton
2012-11-19 14:56 ` [oe] " Denis 'GNUtoo' Carikli
2012-11-19 15:03 ` Philip Balister
2012-11-19 17:15 ` 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=20121119145728.32c62e6c@gnutoo-desktop \
--to=gnutoo@no-log.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=stefan@datenfreihafen.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