From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@openembedded.org
Subject: [PATCH 0/3] A few more updates
Date: Wed, 30 Nov 2011 21:12:29 -0800 [thread overview]
Message-ID: <cover.1322716218.git.sgw@linux.intel.com> (raw)
Richard,
This address the missing checksums and patches from my
last set. Also added here is libffi.
iconv will come later, there was a different problem that I need
to track down.
Sau!
The following changes since commit f4efaa0f472b4bf0ba0a0297cc9ecc8b5a671f72:
squashfs-tools: fix PR, those should start with 'r' (2011-11-30 23:37:40 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib sgw/updates
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/updates
Saul Wold (3):
xserver-xorg*: Update to 1.11.2
gnutls: Update to 2.12.14
libffi: Update to 3.0.10
.../libffi/{libffi_3.0.9.bb => libffi_3.0.10.bb} | 16 +++++++++++-----
...ver-xorg-1.11.1.inc => xserver-xorg-1.11.2.inc} | 7 ++++---
.../crosscompile.patch | 0
.../fix_open_max_preprocessor_error.patch | 0
.../macro_tweak.patch | 0
...-lite_1.11.1.bb => xserver-xorg-lite_1.11.2.bb} | 0
...erver-xorg_1.11.1.bb => xserver-xorg_1.11.2.bb} | 0
.../configure-fix.patch | 0
.../gnutls-2.12.14/fix-gettext-version.patch | 20 ++++++++++++++++++++
.../gnutls-openssl.patch | 0
.../gnutls-texinfo-euro.patch | 0
meta/recipes-support/gnutls/gnutls_2.12.11.bb | 9 ---------
meta/recipes-support/gnutls/gnutls_2.12.14.bb | 10 ++++++++++
13 files changed, 45 insertions(+), 17 deletions(-)
rename meta/recipes-gnome/libffi/{libffi_3.0.9.bb => libffi_3.0.10.bb} (77%)
rename meta/recipes-graphics/xorg-xserver/{xserver-xorg-1.11.1.inc => xserver-xorg-1.11.2.inc} (47%)
rename meta/recipes-graphics/xorg-xserver/{xserver-xorg-1.11.1 => xserver-xorg-1.11.2}/crosscompile.patch (100%)
rename meta/recipes-graphics/xorg-xserver/{xserver-xorg-1.11.1 => xserver-xorg-1.11.2}/fix_open_max_preprocessor_error.patch (100%)
rename meta/recipes-graphics/xorg-xserver/{xserver-xorg-1.11.1 => xserver-xorg-1.11.2}/macro_tweak.patch (100%)
rename meta/recipes-graphics/xorg-xserver/{xserver-xorg-lite_1.11.1.bb => xserver-xorg-lite_1.11.2.bb} (100%)
rename meta/recipes-graphics/xorg-xserver/{xserver-xorg_1.11.1.bb => xserver-xorg_1.11.2.bb} (100%)
rename meta/recipes-support/gnutls/{gnutls-2.12.11 => gnutls-2.12.14}/configure-fix.patch (100%)
create mode 100644 meta/recipes-support/gnutls/gnutls-2.12.14/fix-gettext-version.patch
rename meta/recipes-support/gnutls/{gnutls-2.12.11 => gnutls-2.12.14}/gnutls-openssl.patch (100%)
rename meta/recipes-support/gnutls/{gnutls-2.12.11 => gnutls-2.12.14}/gnutls-texinfo-euro.patch (100%)
delete mode 100644 meta/recipes-support/gnutls/gnutls_2.12.11.bb
create mode 100644 meta/recipes-support/gnutls/gnutls_2.12.14.bb
--
1.7.6.4
next reply other threads:[~2011-12-01 5:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 5:12 Saul Wold [this message]
2011-12-01 5:12 ` [PATCH 1/3] xserver-xorg*: Update to 1.11.2 Saul Wold
2011-12-01 5:12 ` [PATCH 2/3] gnutls: Update to 2.12.14 Saul Wold
2011-12-01 5:12 ` [PATCH 3/3] libffi: Update to 3.0.10 Saul Wold
2011-12-01 10:39 ` [PATCH 0/3] A few more updates Richard Purdie
2011-12-01 10:40 ` Koen Kooi
2011-12-01 10:56 ` 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.1322716218.git.sgw@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-core@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