From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: OE Changelog for 2011-07-11 to 2011-07-18
Date: Mon, 18 Jul 2011 14:57:28 -0700 [thread overview]
Message-ID: <4E24AC48.7050108@mentor.com> (raw)
In-Reply-To: <E1Qivkw-0005IS-9Y@happy.bec-systems.com>
> ====================================================
> Changelog for meta-openembedded:
>
> Khem Raj (2):
> icon-naming-utils: inherit allarch
> icon-naming-utils: Inherit perlnative
[snip]
> Tom Rini (1):
> icon-naming-utils-native: Fix long path to perl in icon-name-mapping
Having just completed my world build in a long build path (pull requests
tomorrow after I sort them out better), why is this in meta-openembedded
and not oe-core? Oversight I assume since I don't see
icon-naming-utils-native coming into oe-core as a recent thing. Or is
there additional stuff in the recipes in meta-openembedded that don't
belong in oe-core?
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2011-07-18 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 21:53 OE Changelog for 2011-07-11 to 2011-07-18 cliff.brake
2011-07-18 21:57 ` Tom Rini [this message]
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=4E24AC48.7050108@mentor.com \
--to=tom_rini@mentor.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