From: Saul Wold <sgw@linux.intel.com>
To: Jack Mitchell <ml@communistcode.co.uk>
Cc: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Improve x11 distro_feature checks
Date: Sat, 27 Oct 2012 18:12:24 -0700 [thread overview]
Message-ID: <508C8678.4000703@linux.intel.com> (raw)
In-Reply-To: <1351258645-14649-1-git-send-email-ml@communistcode.co.uk>
On 10/26/2012 06:37 AM, Jack Mitchell wrote:
> From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
>
> Improvement to the detection of the x11 distro_feature in a few recipes
> with the final achievement being that GTK+ is no longer required in
> core-image-minimal if dbg-pkgs, tools-profile and tools-debug are enabled
> when x11 is not in distro_features.
>
>
> Jack Mitchell (3):
> latencytop: disable GTK and remove gtk+ dependacy
> packagegroup-core-tools-profile: include sysprof only if x11 is
> distro feature
> babeltrace: fix depends
>
These all need PR Bumps.
Thanks
Sau!
> .../packagegroups/packagegroup-core-tools-profile.bb | 4 +++-
> .../latencytop/latencytop-0.5/latencytop-makefile.patch | 13 +++++++------
> meta/recipes-kernel/latencytop/latencytop_0.5.bb | 6 ++++--
> meta/recipes-kernel/lttng-2.0/babeltrace_0.12.bb | 2 +-
> 4 files changed, 15 insertions(+), 10 deletions(-)
>
next prev parent reply other threads:[~2012-10-28 1:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 13:37 [PATCH 0/3] Improve x11 distro_feature checks Jack Mitchell
2012-10-26 13:37 ` [PATCH 1/3] latencytop: disable GTK and remove gtk+ dependacy Jack Mitchell
2012-10-26 13:39 ` Jack Mitchell
2012-10-26 13:37 ` [PATCH 2/3] packagegroup-core-tools-profile: include sysprof only if x11 is distro feature Jack Mitchell
2012-10-26 13:37 ` [PATCH 3/3] babeltrace: fix depends Jack Mitchell
2012-10-28 1:12 ` Saul Wold [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-29 9:28 [PATCH 0/3] Improve x11 distro_feature checks Jack Mitchell
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=508C8678.4000703@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=jack.mitchell@dbbroadcast.co.uk \
--cc=ml@communistcode.co.uk \
--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