From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: poky@yoctoproject.org
Subject: Re: [poky] [PATCH 1/3] Remove machine-specific metadata for machines no longer in oe-core
Date: Thu, 05 May 2011 12:46:08 +0100 [thread overview]
Message-ID: <1304595968.20791.26.camel@rex> (raw)
In-Reply-To: <201105041621.25113.paul.eggleton@linux.intel.com>
On Wed, 2011-05-04 at 16:21 +0100, Paul Eggleton wrote:
> On Wednesday 04 May 2011 16:07:17 Gary Thomas wrote:
> > Perhaps it makes sense to always package netbase in ${MACHINE_ARCH} since
> > it almost always will have machine specific data?
>
> I'll let someone else comment on this, I don't have a hard opinion either way.
Since the exception machines are clearly listed I think its fine as it
stands at the moment. If we start getting lots of overrides there we can
rethink it though. Lets see how it goes...
Cheers,
Richard
next prev parent reply other threads:[~2011-05-05 11:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 14:51 [PATCH 0/3] Remove machine/distro-specific metadata v3 + add some back to meta-yocto Paul Eggleton
2011-05-04 14:51 ` [PATCH 1/3] Remove machine-specific metadata for machines no longer in oe-core Paul Eggleton
2011-05-04 15:07 ` Gary Thomas
2011-05-04 15:21 ` [poky] " Paul Eggleton
2011-05-04 15:31 ` Gary Thomas
2011-05-05 11:46 ` Richard Purdie [this message]
2011-05-04 14:51 ` [PATCH 2/3] Remove distro-specific metadata for distros not " Paul Eggleton
2011-05-04 14:51 ` [PATCH 3/3] meta-yocto: add pieces removed from oe-core for beagleboard & atom-pc Paul Eggleton
2011-05-05 11:38 ` Richard Purdie
2011-05-05 11:46 ` Koen Kooi
2011-05-05 12:21 ` [poky] " Richard Purdie
2011-05-05 12:31 ` Koen Kooi
2011-05-05 12:59 ` Richard Purdie
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=1304595968.20791.26.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.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