From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/4] rootfs space issue along with eglibc and libx11
Date: Fri, 8 Jul 2011 10:29:38 -0700 [thread overview]
Message-ID: <cover.1310145969.git.sgw@linux.intel.com> (raw)
Richard,
This is v2 of my patch set with updated commit messages and
reworked changes. I grabbed the oe-dev change for ldd bashims,
but still included the RDEPENDS for others until the maintainers
update the scripts.
Thanks
Sau!
The following changes since commit 93ce74a299832ca7f24b4ce1b951abffa0232612:
libc-common.bbclass: Fix typo (2011-07-08 18:08:26 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib sgw/fix
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/fix
Saul Wold (4):
rootfs_rpm: Add 50M to IMAGE_ROOTFS_EXTRA_SPACE for zypper /var space
eglibc: unbash ldd (from oe.dev)
eglibc: add RDEPENDS for bash on eglibc-utils
libx11: enable xcb support
meta/classes/rootfs_rpm.bbclass | 5 +++++
meta/recipes-core/eglibc/eglibc-package.inc | 2 +-
meta/recipes-core/eglibc/eglibc.inc | 3 +--
meta/recipes-graphics/xorg-lib/libx11_1.3.4.bb | 11 ++++++++---
4 files changed, 15 insertions(+), 6 deletions(-)
--
1.7.3.4
next reply other threads:[~2011-07-08 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 17:29 Saul Wold [this message]
2011-07-08 17:29 ` [PATCH v2 1/4] rootfs_rpm: Add 50M to IMAGE_ROOTFS_EXTRA_SPACE for zypper /var space Saul Wold
2011-07-08 17:29 ` [PATCH v2 2/4] eglibc: unbash ldd (from oe.dev) Saul Wold
2011-07-08 17:29 ` [PATCH v2 3/4] eglibc: add RDEPENDS for bash on eglibc-utils Saul Wold
2011-07-08 17:29 ` [PATCH v2 4/4] libx11: enable xcb support Saul Wold
2011-07-08 22:02 ` [PATCH v2 0/4] rootfs space issue along with eglibc and libx11 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.1310145969.git.sgw@linux.intel.com \
--to=sgw@linux.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