From: Armin Kuster <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org, otavio@ossystems.com.br
Subject: [PATCH 00/11] [Dizzy next] pull merge request
Date: Fri, 23 Jan 2015 14:53:40 -0800 [thread overview]
Message-ID: <cover.1422053452.git.akuster808@gmail.com> (raw)
Please consider this changes for meta-openembedded dizzy
The following changes since commit 3b83aa44186fac44a679cd24a5ae64560cb4118f:
xf86-video-glamo: fix build with xserver 1.16 (2015-01-18 16:40:55 -0800)
are available in the git repository at:
git://github.com/akuster/meta-openembedded akuster/dizzy-next
https://github.com/akuster/meta-openembedded/tree/akuster/dizzy-next
Belal, Awais (1):
iperf: fix out of tree configuration
Jackie Huang (8):
meta-gnome: Add LAYERVERSION and LAYERDEPENDS
meta-perl: Add LAYERVERSION and LAYERDEPENDS
meta-python: Add LAYERVERSION and LAYERDEPENDS
meta-ruby: Add LAYERVERSION and LAYERDEPENDS
toolchain-layer: Add LAYERVERSION and LAYERDEPENDS
meta-efl: Add LAYERVERSION and LAYERDEPENDS
meta-filesystems: Add LAYERVERSION and LAYERDEPENDS
meta-gpe: Add LAYERVERSION and LAYERDEPENDS
Otavio Salvador (1):
nbench-byte: Fix license QA error
Qi.Chen@windriver.com (1):
xmlto: remove recipe as it's in OE core
meta-efl/conf/layer.conf | 6 +++
meta-filesystems/conf/layer.conf | 6 +++
meta-gnome/conf/layer.conf | 6 +++
meta-gpe/conf/layer.conf | 6 +++
meta-oe/licenses/nbench-byte | 10 +++++
.../iperf-2.0.5/0001-fix-out-of-tree-config.patch | 52 ++++++++++++++++++++++
meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb | 1 +
.../nbench-byte/nbench-byte_2.2.3.bb | 2 +-
.../xmlto-0.0.25/obsolete_automake_macros.patch | 12 -----
meta-oe/recipes-support/xmlto/xmlto_0.0.25.bb | 18 --------
meta-perl/conf/layer.conf | 6 +++
meta-python/conf/layer.conf | 6 +++
meta-ruby/conf/layer.conf | 6 +++
toolchain-layer/conf/layer.conf | 5 +++
14 files changed, 111 insertions(+), 31 deletions(-)
create mode 100644 meta-oe/licenses/nbench-byte
create mode 100644 meta-oe/recipes-benchmark/iperf/iperf-2.0.5/0001-fix-out-of-tree-config.patch
delete mode 100644 meta-oe/recipes-support/xmlto/xmlto-0.0.25/obsolete_automake_macros.patch
delete mode 100644 meta-oe/recipes-support/xmlto/xmlto_0.0.25.bb
--
1.9.1
next reply other threads:[~2015-01-23 22:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 22:53 Armin Kuster [this message]
2015-01-23 22:53 ` [PATCH 01/11] iperf: fix out of tree configuration Armin Kuster
2015-01-24 9:09 ` Koen Kooi
2015-01-26 15:37 ` akuster808
2015-01-23 22:53 ` [PATCH 02/11] meta-gnome: Add LAYERVERSION and LAYERDEPENDS Armin Kuster
2015-01-23 22:53 ` [PATCH 03/11] meta-perl: " Armin Kuster
2015-01-23 22:53 ` [PATCH 04/11] meta-python: " Armin Kuster
2015-01-23 22:53 ` [PATCH 05/11] meta-ruby: " Armin Kuster
2015-01-23 22:53 ` [PATCH 06/11] toolchain-layer: " Armin Kuster
2015-01-23 22:53 ` [PATCH 07/11] meta-efl: " Armin Kuster
2015-01-23 22:53 ` [PATCH 08/11] meta-filesystems: " Armin Kuster
2015-01-23 22:53 ` [PATCH 09/11] meta-gpe: " Armin Kuster
2015-01-23 22:53 ` [PATCH 10/11] nbench-byte: Fix license QA error Armin Kuster
2015-01-23 22:53 ` [PATCH 11/11] xmlto: remove recipe as it's in OE core Armin Kuster
2015-01-24 0:50 ` [PATCH 00/11] [Dizzy next] pull merge request Otavio Salvador
2015-01-28 8:19 ` Martin Jansa
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=cover.1422053452.git.akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.