Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Bring in overlayed recipe from meta-oe
Date: Wed,  3 Apr 2013 19:27:23 +0100	[thread overview]
Message-ID: <cover.1365013369.git.paul.eggleton@linux.intel.com> (raw)

This is one of the last remaining recipes from meta-oe that we need to
bring over to OE-Core. I realise this is late in the cycle, but the
impact should be minimal and would help reduce the overlap of meta-oe
which is a beneficial thing in itself. I have tested building and
running a Sato image with it applied and there was no apparent change
in the icons or indicated by buildhistory for sato-icon-theme which
seems to be the only item we have that depends upon
icon-naming-utils(-native).



The following change since commit ca36be708e54c0c86535bc8512295c76c48f6cf5:

  classes/sstate: avoid traceback when no files have been staged (2013-04-03 17:01:09 +0100)

is available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/meta-oe-cleanup
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/meta-oe-cleanup

Paul Eggleton (1):
  icon-naming-utils: import version 0.8.90 from meta-oe

 ...tils-native_0.8.7.bb => icon-naming-utils_0.8.90.bb} |   15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)
 rename meta/recipes-devtools/icon-naming-utils/{icon-naming-utils-native_0.8.7.bb => icon-naming-utils_0.8.90.bb} (58%)

-- 
1.7.10.4




             reply	other threads:[~2013-04-03 18:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 18:27 Paul Eggleton [this message]
2013-04-03 18:27 ` [PATCH 1/1] icon-naming-utils: import version 0.8.90 from meta-oe Paul Eggleton

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=cover.1365013369.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.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