From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] pseudo update (1.3.1)
Date: Thu, 5 Jul 2012 13:25:57 -0500 [thread overview]
Message-ID: <cover.1341512659.git.peter.seebach@windriver.com> (raw)
The big change is a bug fix for path expansion inside a chroot,
which could cause memory corruption errors.
The following changes since commit dcc43c34bfa9304233ecfd3f518a84ddfdc2fd90:
Tom Zanussi (1):
perf: remove unconditional python-ext install
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/pseudo
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo
Peter Seebach (1):
pseudo: Update to 1.3.1 (fixing chroot crash)
meta/recipes-devtools/pseudo/pseudo_1.3.1.bb | 8 ++++++++
meta/recipes-devtools/pseudo/pseudo_1.3.bb | 8 --------
meta/recipes-devtools/pseudo/pseudo_git.bb | 6 +++---
3 files changed, 11 insertions(+), 11 deletions(-)
create mode 100644 meta/recipes-devtools/pseudo/pseudo_1.3.1.bb
delete mode 100644 meta/recipes-devtools/pseudo/pseudo_1.3.bb
next reply other threads:[~2012-07-05 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 18:25 Peter Seebach [this message]
2012-07-05 18:25 ` [PATCH 1/1] pseudo: Update to 1.3.1 (fixing chroot crash) Peter Seebach
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.1341512659.git.peter.seebach@windriver.com \
--to=peter.seebach@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