From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] denzil pull request 3
Date: Mon, 18 Jun 2012 12:57:54 -0700 [thread overview]
Message-ID: <cover.1340038108.git.scott.a.garman@intel.com> (raw)
Hello,
This is the third pull request for the oe-core denzil branch, based on
a set of commits I've been testing from my sgarman/denzil-next branch.
These commits have undergone the following testing on the autobuilder:
nightly:
nightly-multilib:
http://autobuilder.yoctoproject.org:8010/builders/nightly-multilib/builds/114
nightly-non-gpl3:
http://autobuilder.yoctoproject.org:8010/builders/nightly-non-gpl3/builds/115
nightly-tiny:
http://autobuilder.yoctoproject.org:8010/builders/nightly-tiny/builds/97
nightly-meta-intel:
http://autobuilder.yoctoproject.org:8010/builders/nightly-meta-intel/builds/106
I'll note these tests were done with the poky-based tree.
Scott
The following changes since commit 7c767d3723e0b55d3bcd3864a9cdbce6d11d5b35:
freetype: upgrade to 2.4.9 (2012-06-12 13:29:31 -0700)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib sgarman/denzil-next-testing
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgarman/denzil-next-pull3
Gary Thomas (1):
webkit-gtk: Apply work around for all PowerPC targets
Laurentiu Palcu (1):
sanity.bbclass: warn the user if BBPATH contains wrong entries
Nitin A Kamble (1):
eglibc: package mtrace separately
Richard Purdie (1):
openjade-native: Ensure we reautoconf the package
Saul Wold (2):
quilt: added ac_cv_path_BASH to CACHED_CONFIGUREVARS
eglibc: added ac_cv_path_ to CACHED_CONFIGUREVARS
meta/classes/sanity.bbclass | 13 ++-
meta/recipes-core/eglibc/eglibc-package.inc | 7 +-
meta/recipes-core/eglibc/eglibc.inc | 2 +
meta/recipes-core/eglibc/eglibc_2.13.bb | 2 +-
meta/recipes-core/eglibc/eglibc_2.15.bb | 2 +-
meta/recipes-core/tasks/task-core-tools-debug.bb | 4 +
.../openjade/openjade-1.3.2/reautoconf.patch | 83 ++++++++++++++++++++
.../openjade/openjade-native_1.3.2.bb | 5 ++
meta/recipes-devtools/quilt/quilt_0.51.bb | 5 +-
meta/recipes-sato/webkit/webkit-gtk_svn.bb | 15 ++--
10 files changed, 127 insertions(+), 11 deletions(-)
create mode 100644 meta/recipes-devtools/openjade/openjade-1.3.2/reautoconf.patch
--
1.7.9.5
next reply other threads:[~2012-06-18 20:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 19:57 Scott Garman [this message]
2012-06-18 19:57 ` [PATCH 1/6] openjade-native: Ensure we reautoconf the package Scott Garman
2012-06-18 19:57 ` [PATCH 2/6] webkit-gtk: Apply work around for all PowerPC targets Scott Garman
2012-06-18 19:57 ` [PATCH 3/6] sanity.bbclass: warn the user if BBPATH contains wrong entries Scott Garman
2012-06-21 10:54 ` Richard Purdie
2012-06-18 19:57 ` [PATCH 4/6] eglibc: package mtrace separately Scott Garman
2012-06-18 19:57 ` [PATCH 5/6] quilt: added ac_cv_path_BASH to CACHED_CONFIGUREVARS Scott Garman
2012-06-18 19:58 ` [PATCH 6/6] eglibc: added ac_cv_path_ " Scott Garman
2012-06-18 20:01 ` [PATCH 0/6] denzil pull request 3 Scott Garman
2012-06-21 11:00 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2012-10-05 19:52 Scott Garman
2012-10-05 20:16 ` McClintock Matthew-B29882
2012-10-10 15:40 ` Scott Garman
2012-10-10 22:30 ` Richard Purdie
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.1340038108.git.scott.a.garman@intel.com \
--to=scott.a.garman@intel.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