From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/3] bitbake-layers: flatten improvements
Date: Tue, 10 Jan 2012 17:44:10 +0000 [thread overview]
Message-ID: <1326217450.23315.0.camel@ted> (raw)
In-Reply-To: <cover.1326023910.git.paul.eggleton@linux.intel.com>
On Sun, 2012-01-08 at 12:06 +0000, Paul Eggleton wrote:
> A few patches improving the "flatten" subcommand in bitbake-layers,
> prompted by Yocto bug #1654, to allow only flattening some of the
> configured layers as well as warn when recipes/bbappends are outside
> the new flattened layer's paths. I'm hoping to be able to improve it
> further in future to be able to automatically put files in the
> correct place but this will have to wait until the next development
> cycle.
>
> The patches (against Poky, but which apply cleanly against bitbake
> master with -p2) are available in the git repository at:
> git://git.yoctoproject.org/poky-contrib paule/bitbake-layers-fix4
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bitbake-layers-fix4
>
> Paul Eggleton (3):
> bitbake-layers: flatten: allow specifying layers to flatten
> bitbake-layers: flatten: warn the user if output structure is
> incorrect
> bitbake-layers: close files in apply_append()
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-01-10 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 12:06 [PATCH 0/3] bitbake-layers: flatten improvements Paul Eggleton
2012-01-08 12:06 ` [PATCH 1/3] bitbake-layers: flatten: allow specifying layers to flatten Paul Eggleton
2012-01-08 12:06 ` [PATCH 2/3] bitbake-layers: flatten: warn the user if output structure is incorrect Paul Eggleton
2012-01-08 12:06 ` [PATCH 3/3] bitbake-layers: close files in apply_append() Paul Eggleton
2012-01-10 17:44 ` 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=1326217450.23315.0.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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