From: Kang Kai <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: [PATCH 0/1] Fix rpm2cpio segment fault
Date: Thu, 28 Feb 2013 15:34:38 +0800 [thread overview]
Message-ID: <cover.1362035905.git.kai.kang@windriver.com> (raw)
The following changes since commit d7b248e715d99766bf8602ff9f038f8b0afa5e78:
augeas: change SRC_URI (2013-02-26 08:02:29 -0800)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib kangkai/fix-rpm2cpio
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/fix-rpm2cpio
Kang Kai (1):
rpm: fix rpm2cpio segmentation fault
.../rpm/rpm/rpm2cpio-fix-segmentation-fault.patch | 24 ++++++++++++++++++++
meta/recipes-devtools/rpm/rpm_5.4.9.bb | 3 +-
2 files changed, 26 insertions(+), 1 deletions(-)
create mode 100644 meta/recipes-devtools/rpm/rpm/rpm2cpio-fix-segmentation-fault.patch
--
1.7.5.4
next reply other threads:[~2013-02-28 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 7:34 Kang Kai [this message]
2013-02-28 7:34 ` [PATCH 1/1] rpm: fix rpm2cpio segmentation fault Kang Kai
2013-02-28 14:34 ` Mark Hatle
2013-03-12 5:57 ` Kang Kai
2013-03-12 15:30 ` Mark Hatle
2013-04-12 9:18 ` Kang Kai
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.1362035905.git.kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=Zhenfeng.Zhao@windriver.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