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/6] bitbake-layers improvements
Date: Wed, 01 Feb 2012 15:10:15 +0000 [thread overview]
Message-ID: <1328109015.13744.74.camel@ted> (raw)
In-Reply-To: <cover.1327940413.git.paul.eggleton@linux.intel.com>
On Mon, 2012-01-30 at 16:25 +0000, Paul Eggleton wrote:
> Make some significant improvements to bitbake-layers that should provide
> more information about what files each layer is overlaying as well as
> making the utility easier to use.
>
> The following changes (against Poky, but apply cleanly with -p2 against
> bitbake master) are available in the git repository at:
> git://git.yoctoproject.org/poky-contrib paule/bitbake-layers-fix5
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bitbake-layers-fix5
>
> Paul Eggleton (6):
> bitbake-layers: add copyright notice
> bitbake-layers: use dashes in subcommands
> bitbake-layers: use directory name as layer name
> bitbake-layers: improve show-overlayed output
> bitbake-layers: add show-recipes subcommand
> bitbake-layers: list overlayed classes in show-overlayed
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-02-01 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 16:25 [PATCH 0/6] bitbake-layers improvements Paul Eggleton
2012-01-30 16:25 ` [PATCH 1/6] bitbake-layers: add copyright notice Paul Eggleton
2012-01-30 16:25 ` [PATCH 2/6] bitbake-layers: use dashes in subcommands Paul Eggleton
2012-01-30 16:25 ` [PATCH 3/6] bitbake-layers: use directory name as layer name Paul Eggleton
2012-01-30 16:25 ` [PATCH 4/6] bitbake-layers: improve show-overlayed output Paul Eggleton
2012-01-30 16:25 ` [PATCH 5/6] bitbake-layers: add show-recipes subcommand Paul Eggleton
2012-01-30 16:25 ` [PATCH 6/6] bitbake-layers: list overlayed classes in show-overlayed Paul Eggleton
2012-02-01 15:10 ` 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=1328109015.13744.74.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 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.