From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
Scott Garman <scott.a.garman@intel.com>
Subject: [denzil][PATCH 0/4] Fixes for denzil-next
Date: Fri, 10 Aug 2012 17:09:03 +0100 [thread overview]
Message-ID: <cover.1344614803.git.paul.eggleton@linux.intel.com> (raw)
Some cherry-picks from master to fix bugs in denzil.
The following changes since commit 741146fa90f28f7ce8d82ee7f7e254872d519724:
gconf.bbclass: don't register schemas in the install stage (2012-06-29 15:03:01 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/denzil-fixes-core
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/denzil-fixes-core
Paul Eggleton (4):
classes/rootfs_*: fix splitting package dependency strings
buildhistory_analysis: fix error when version specifier missing
scripts/buildhistory-diff: add GitPython version check
classes/license: fix manifest to work with deb
meta/classes/license.bbclass | 2 +-
meta/classes/rootfs_deb.bbclass | 4 ++--
meta/classes/rootfs_ipk.bbclass | 4 ++--
meta/lib/oe/buildhistory_analysis.py | 2 +-
scripts/buildhistory-diff | 8 ++++++--
5 files changed, 12 insertions(+), 8 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-08-10 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 16:09 Paul Eggleton [this message]
2012-08-10 16:09 ` [denzil][PATCH 1/4] classes/rootfs_*: fix splitting package dependency strings Paul Eggleton
2012-08-10 16:09 ` [denzil][PATCH 2/4] buildhistory_analysis: fix error when version specifier missing Paul Eggleton
2012-08-10 16:09 ` [denzil][PATCH 3/4] scripts/buildhistory-diff: add GitPython version check Paul Eggleton
2012-08-10 16:09 ` [denzil][PATCH 4/4] classes/license: fix manifest to work with deb Paul Eggleton
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.1344614803.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.a.garman@intel.com \
/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