From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
Scott Garman <scott.a.garman@intel.com>
Subject: [PATCH 0/1] Fix buildhistory depgraphs with ipk/deb
Date: Sun, 13 May 2012 09:52:56 +0100 [thread overview]
Message-ID: <cover.1336898939.git.paul.eggleton@linux.intel.com> (raw)
This fix should also go into 1.2.1.
The following change since commit cab85fd0b481cdbf36477348de75352be3f38ca2:
gdk-pixbuf: Drop unneeded RPROVIDES (2012-05-12 11:23:27 +0100)
is available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-depgraph-fix
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/buildhistory-depgraph-fix
Paul Eggleton (1):
classes/rootfs_*: fix splitting package dependency strings
meta/classes/rootfs_deb.bbclass | 4 ++--
meta/classes/rootfs_ipk.bbclass | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-05-13 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 8:52 Paul Eggleton [this message]
2012-05-13 8:52 ` [PATCH 1/1] classes/rootfs_*: fix splitting package dependency strings Paul Eggleton
2012-05-16 18:18 ` 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.1336898939.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