Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] v2 Import the blacklist functionality from meta-oe
Date: Wed, 9 May 2012 15:00:05 -0500	[thread overview]
Message-ID: <cover.1336593352.git.mark.hatle@windriver.com> (raw)

Refactor from v1.  Include the original functionality from meta-oe, it
has been changed based on comments both on the list and off.  And I believe
greatly simplified.

It is expected that distributions who need the old functionality may
continue to use the old blacklist.bbclass in their layers.

One additional note, I had people ask why I need this functionality.  The
issue is that we intend to use OE-Core release almost exactly as-is.  But
we have to sent reasonable support boundries for our customers.  This will
allow us to declare certain items as unsupported, and if the end user
wishes to clear the blacklist they can.

The following changes since commit 043871d7e5d2d19c2ff43e54d2ff180c09e8903e:

  kern-tools: integrate minor fixes (2012-05-08 16:06:15 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib mhatle/blacklist
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/blacklist

Mark Hatle (2):
  blacklist: fix typo in name
  blacklist.bbclass: Refactor, use PNBLACKLIST[pn]

 meta/classes/blacklist.bbclass |   20 ++++++++++++++++++++
 1 files changed, 20 insertions(+), 0 deletions(-)
 create mode 100644 meta/classes/blacklist.bbclass

-- 
1.7.3.4




             reply	other threads:[~2012-05-09 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 20:00 Mark Hatle [this message]
2012-05-09 20:00 ` [PATCH 1/2] blacklist: fix typo in name Mark Hatle
2012-05-09 20:00 ` [PATCH 2/2 v2] blacklist.bbclass: Refactor, use PNBLACKLIST[pn] Mark Hatle
2012-05-09 20:45   ` Koen Kooi
2012-05-09 21:16     ` Mark Hatle

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.1336593352.git.mark.hatle@windriver.com \
    --to=mark.hatle@windriver.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