From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] fix RPM rootfs issue for ATTEMPTONLY
Date: Thu, 11 Aug 2011 17:09:50 -0700 [thread overview]
Message-ID: <cover.1313107646.git.sgw@linux.intel.com> (raw)
Richard:
This issue was introduced with the recent IMAGE_FEATURES changes,
since the ATTEMPTONLY was not really being used it had not been updated
for some of the MultiLib changes, this fixes that situation.
Thanks
Sau!
The following changes since commit a92d56058b21913570bb17ae416c3b00afce055e:
gnome-doc-utils: respect python-dir setting EXTRA_OECONF (2011-08-11 19:13:38 +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 (1):
package_rpm: fix up attemptonly code
meta/classes/package_rpm.bbclass | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
--
1.7.3.4
next reply other threads:[~2011-08-12 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 0:09 Saul Wold [this message]
2011-08-12 0:09 ` [PATCH 1/1] package_rpm: fix up attemptonly code Saul Wold
2011-08-12 0:27 ` [PATCH 0/1] fix RPM rootfs issue for ATTEMPTONLY Mark Hatle
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.1313107646.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