All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Make PNBLACKLIST work with multilibs, code cleanup
Date: Thu, 16 Aug 2012 11:31:54 -0700	[thread overview]
Message-ID: <502D3C9A.7050303@linux.intel.com> (raw)
In-Reply-To: <cover.1344639098.git.peter.seebach@windriver.com>

On 08/10/2012 03:57 PM, Peter Seebach wrote:
> First, make PNBLACKLIST work with multilib builds.
>
> Second, just some quick cleanup of the multilib logic that handles
> PREFERRED_PROVIDER, PREFERRED_VERSION, and now also PNBLACKLIST.
>
> The following changes since commit 5290e82ecef08b5e573d7442627276d7b42c6b93:
>    Saul Wold (1):
>          foomatic: fix perl path for target
>
> are available in the git repository at:
>
>    git://git.yoctoproject.org/poky-contrib seebs/blacklist
>    http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/blacklist
>
> Peter Seebach (2):
>    base.bbclass: Expand PNBLACKLIST across multilibs too
>    base.bbclass: Restructure multilib variable cloning
>
>   meta/classes/base.bbclass |   60 +++++++++++++++++++++++++-------------------
>   1 files changed, 34 insertions(+), 26 deletions(-)
>
Merged into OE-Core

Thanks
	Sau!

>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



      parent reply	other threads:[~2012-08-16 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 22:57 [PATCH 0/2] Make PNBLACKLIST work with multilibs, code cleanup Peter Seebach
2012-08-10 22:57 ` [PATCH 1/2] base.bbclass: Expand PNBLACKLIST across multilibs too Peter Seebach
2012-08-10 23:13   ` Peter Seebach
2012-08-10 22:58 ` [PATCH 2/2] base.bbclass: Restructure multilib variable cloning Peter Seebach
2012-08-16 18:31 ` Saul Wold [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=502D3C9A.7050303@linux.intel.com \
    --to=sgw@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 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.