From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Misc core cleanups
Date: Thu, 23 Jun 2011 13:27:25 +0100 [thread overview]
Message-ID: <cover.1308831847.git.richard.purdie@linuxfoundation.org> (raw)
Following are four proposed cleanups for the core classes.
The patches are available on the end of the branch in the git repository at:
git://git.pokylinux.org/poky-contrib rpurdie/wip
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=rpurdie/wip
Richard Purdie (4):
base.bbclass: Drop old style SRCDATE handling, we have pn- overrides
now
base.bbclass: Since we require python 2.6 which always contains
hashlib we can drop this fallback code
classes/conf: Drop MULTIMACH_ARCH variable, it adds unused complexity
and serves no useful purpose
base/glib-2.0: Simplify USE_NLS handling for glib-2.0
meta/classes/base.bbclass | 27 +--------------------------
meta/classes/cross-canadian.bbclass | 14 +++++++-------
meta/classes/sstate.bbclass | 4 ++--
meta/conf/bitbake.conf | 9 ++-------
meta/conf/distro/include/tclibc-uclibc.inc | 1 -
meta/recipes-core/glib-2.0/glib-2.0.inc | 6 ------
meta/recipes-core/glib-2.0/glib.inc | 3 +--
7 files changed, 13 insertions(+), 51 deletions(-)
delete mode 100644 meta/recipes-core/glib-2.0/glib-2.0.inc
--
1.7.4.1
next reply other threads:[~2011-06-23 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 12:27 Richard Purdie [this message]
2011-06-23 12:27 ` [PATCH 1/4] base.bbclass: Drop old style SRCDATE handling, we have pn- overrides now Richard Purdie
2011-06-23 12:27 ` [PATCH 2/4] base.bbclass: Since we require python 2.6 which always contains hashlib we can drop this fallback code Richard Purdie
2011-06-23 12:27 ` [PATCH 3/4] classes/conf: Drop MULTIMACH_ARCH variable, it adds unused complexity and serves no useful purpose Richard Purdie
2011-06-23 12:27 ` [PATCH 4/4] base/glib-2.0: Simplify USE_NLS handling for glib-2.0 Richard Purdie
2011-06-23 23:46 ` 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=cover.1308831847.git.richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.