Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Chris Larson <chris_larson@mentor.com>
Subject: Re: [PATCH 0/5] Variable typing & reworked imports handling
Date: Fri, 20 May 2011 17:40:22 +0100	[thread overview]
Message-ID: <1305909623.3424.661.camel@rex> (raw)
In-Reply-To: <cover.1305752502.git.chris_larson@mentor.com>

On Wed, 2011-05-18 at 14:02 -0700, Chris Larson wrote:
> From: Chris Larson <chris_larson@mentor.com>
> 
> Pull URL: git://git.openembedded.org/openembedded-core-contrib
>   Branch: kergoth/oe-sync-base
>   Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kergoth/oe-sync-base
> 
> Thanks,
>     Chris Larson <chris_larson@mentor.com>
> ---
> 
> 
> Chris Larson (5):
>   Implement variable typing (sync from OE)
>   oe.data: expand the flags
>   base.bbclass: switch to current OE's imports handling
>   Shift oe import logic out of the event handler
>   base.bbclass: use oe.data for OE_IMPORTS

Merged to master, thanks.

Richard




      parent reply	other threads:[~2011-05-20 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 21:02 [PATCH 0/5] Variable typing & reworked imports handling Chris Larson
2011-05-18 21:02 ` [PATCH 1/5] Implement variable typing (sync from OE) Chris Larson
2011-05-18 21:02 ` [PATCH 2/5] oe.data: expand the flags Chris Larson
2011-05-18 21:02 ` [PATCH 3/5] base.bbclass: switch to current OE's imports handling Chris Larson
2011-05-18 21:02 ` [PATCH 4/5] Shift oe import logic out of the event handler Chris Larson
2011-05-18 21:02 ` [PATCH 5/5] base.bbclass: use oe.data for OE_IMPORTS Chris Larson
2011-05-20  0:21 ` [PATCH 0/5] Variable typing & reworked imports handling Joshua Lock
2011-05-20 16:40 ` Richard Purdie [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=1305909623.3424.661.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=chris_larson@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