From: Otavio Salvador <otavio@ossystems.com.br>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Pending patches in O.S. Systems' tree
Date: Fri, 24 Feb 2012 20:50:52 +0000 [thread overview]
Message-ID: <cover.1330116559.git.otavio@ossystems.com.br> (raw)
The following changes since commit 22194a04f224864dd687660e351a3a10da1f06fa:
scripts/hob: Launch the new hob (2012-02-24 18:05:46 +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 (2):
qt4-native: set headerdir as done in regular builds
useradd.bbclass: override USERADDSETSCENEDEPS to empty when building
cross packages
meta/classes/useradd.bbclass | 1 +
meta/recipes-qt/qt4/qt4-native.inc | 3 ++-
2 files changed, 3 insertions(+), 1 deletions(-)
--
1.7.2.5
next reply other threads:[~2012-02-24 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 20:50 Otavio Salvador [this message]
2012-02-24 20:50 ` [PATCH 1/2] qt4-native: set headerdir as done in regular builds Otavio Salvador
2012-02-24 20:50 ` [PATCH 2/2] useradd.bbclass: override USERADDSETSCENEDEPS to empty when building cross packages Otavio Salvador
2012-02-26 1:50 ` [PATCH 0/2] Pending patches in 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.1330116559.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