From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] turning conf/machine into a set of bblayers
Date: Thu, 04 Nov 2010 08:48:51 +0100 [thread overview]
Message-ID: <iatoh3$1mq$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTiknWyRh2L9u9jbgYgvK5dXx7x2VFeKGhh89TAxJ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03-11-10 21:44, Khem Raj wrote:
> I dont think it would make sense to put things like gcc and binutils
> and core components
> into overlays.
I would put those into a 'devtools' layer, like poky has done.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFM0mVjMkyGM64RGpERAspiAKCCVvbm5EWD3OejRvjSCxAxbBEsoQCfVjND
kvkJ8A0aRkuCV5lP28eXLas=
=rw7D
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-11-04 7:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 9:33 [RFC] turning conf/machine into a set of bblayers Koen Kooi
2010-10-21 9:52 ` Graeme Gregory
2010-10-21 9:59 ` Koen Kooi
2010-10-21 10:04 ` Graeme Gregory
2010-10-21 10:17 ` Frans Meulenbroeks
2010-10-21 10:20 ` Frans Meulenbroeks
2010-10-21 10:38 ` Richard Purdie
2010-10-21 12:01 ` Frans Meulenbroeks
2010-10-21 13:46 ` Maupin, Chase
2010-10-21 14:21 ` Chris Larson
2010-10-21 16:11 ` Denys Dmytriyenko
2010-11-01 21:04 ` Tom Rini
2010-10-21 10:48 ` Richard Purdie
2010-10-21 11:22 ` Graeme Gregory
2010-10-21 14:21 ` Chris Larson
2010-10-21 10:36 ` Richard Purdie
2010-11-02 7:02 ` Frans Meulenbroeks
2010-11-02 20:46 ` Koen Kooi
2010-11-02 21:14 ` Eric Bénard
2010-11-02 21:19 ` Koen Kooi
2010-11-02 21:21 ` Tom Rini
2010-11-03 8:15 ` Frans Meulenbroeks
2010-11-03 14:59 ` Tom Rini
2010-11-03 18:59 ` Frans Meulenbroeks
2010-11-03 20:17 ` Tom Rini
2010-11-03 20:44 ` Khem Raj
2010-11-03 21:06 ` Frans Meulenbroeks
2010-11-03 22:13 ` Khem Raj
2010-11-04 7:48 ` Koen Kooi [this message]
2010-11-02 21:57 ` 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='iatoh3$1mq$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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