From: Otavio Salvador <otavio@ossystems.com.br>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/10] Pending patches from O.S. Systems tree
Date: Thu, 5 Jan 2012 19:37:50 +0000 [thread overview]
Message-ID: <cover.1325792209.git.otavio@ossystems.com.br> (raw)
The following changes since commit 563828bad19a242bba9ce3db461bb5807037dfdf:
multilib: Abstract class extension code into classextend.py (2012-01-05 12:36:08 +0000)
are available in the git repository at:
git://github.com/OSSystems/oe-core master
https://github.com/OSSystems/oe-core/tree/HEAD
Otavio Salvador (10):
qt4-graphics-system: add
qt4e.bbclass: add QT_BASE_NAME for use in recipes
qt4x11.bbclass: add QT_BASE_NAME for use in recipes
qt4-embedded.inc: use QT_BASE_NAME from qt4e.bbclass
qt4-x11-free.inc: use QT_BASE_NAME from qt4x11.bbclass
initscripts: avoid mounting /sys if it is already mounted
busybox: disable syslogd configuration file support
udev: ensure /dev/pts and /dev/shm does exists
udev: improve udev-cache robustness
udev: drop depmod handling code as it ought to be done in kernel
postinst
meta/classes/qt4e.bbclass | 1 +
meta/classes/qt4x11.bbclass | 1 +
meta/recipes-core/busybox/busybox-1.19.3/defconfig | 2 +-
meta/recipes-core/busybox/busybox_1.19.3.bb | 2 +-
.../initscripts/initscripts-1.0/sysfs.sh | 4 +-
meta/recipes-core/initscripts/initscripts_1.0.bb | 2 +-
meta/recipes-core/udev/udev.inc | 11 +++++++-
meta/recipes-core/udev/udev/init | 23 +++++++++++++---
meta/recipes-core/udev/udev/udev-cache | 20 ++++++++++++--
meta/recipes-core/udev/udev/udev-cache.default | 4 +++
meta/recipes-core/udev/udev_164.bb | 2 +-
.../qt4-graphics-system/qt4-graphics-system_1.0.bb | 27 ++++++++++++++++++++
meta/recipes-qt/qt4/qt4-embedded.inc | 3 +-
meta/recipes-qt/qt4/qt4-x11-free.inc | 3 +-
14 files changed, 86 insertions(+), 19 deletions(-)
create mode 100644 meta/recipes-core/udev/udev/udev-cache.default
create mode 100644 meta/recipes-qt/qt4-graphics-system/qt4-graphics-system_1.0.bb
--
1.7.2.5
next reply other threads:[~2012-01-05 19:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 19:37 Otavio Salvador [this message]
2012-01-05 19:37 ` [PATCH 01/10] qt4-graphics-system: add Otavio Salvador
2012-01-05 22:03 ` Saul Wold
2012-01-05 22:07 ` Otavio Salvador
2012-01-05 19:37 ` [PATCH 02/10] qt4e.bbclass: add QT_BASE_NAME for use in recipes Otavio Salvador
2012-01-05 19:37 ` [PATCH 03/10] qt4x11.bbclass: " Otavio Salvador
2012-01-05 19:37 ` [PATCH 04/10] qt4-embedded.inc: use QT_BASE_NAME from qt4e.bbclass Otavio Salvador
2012-01-05 19:37 ` [PATCH 05/10] qt4-x11-free.inc: use QT_BASE_NAME from qt4x11.bbclass Otavio Salvador
2012-01-05 19:37 ` [PATCH 06/10] initscripts: avoid mounting /sys if it is already mounted Otavio Salvador
2012-01-05 19:37 ` [PATCH 07/10] busybox: disable syslogd configuration file support Otavio Salvador
2012-01-05 19:37 ` [PATCH 08/10] udev: ensure /dev/pts and /dev/shm does exists Otavio Salvador
2012-01-05 19:37 ` [PATCH 09/10] udev: improve udev-cache robustness Otavio Salvador
2012-01-05 19:38 ` [PATCH 10/10] udev: drop depmod handling code as it ought to be done in kernel postinst Otavio Salvador
2012-01-05 22:07 ` Saul Wold
2012-01-05 22:09 ` Otavio Salvador
2012-01-05 22:22 ` Otavio Salvador
2012-01-09 6:00 ` [PATCH 00/10] Pending patches from O.S. Systems tree Saul Wold
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.1325792209.git.otavio@ossystems.com.br \
--to=otavio@ossystems.com.br \
--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