From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] *** SUBJECT HERE *** (huh?)
Date: Mon, 09 Jul 2012 09:51:56 -0700 [thread overview]
Message-ID: <4FFB0C2C.2080003@linux.intel.com> (raw)
In-Reply-To: <cover.1341365770.git.peter.seebach@windriver.com>
On 07/03/2012 06:37 PM, Peter Seebach wrote:
> Robert Yang identified a crash with chroot in long directories,
> which was a logic bug in the allocate-and-copy logic when
> expanding paths inside a base path. Fixed in upstream pseudo,
> along with a couple of other minor tweaks, since the crash is
> blocking other work we should probably update.
>
> The following changes since commit a6b6df1350149c116050cb93c3c7b4802c709d31:
> Lianhao Lu (1):
> task-core-tools-debug: Added openssh-sftp-server.
>
> 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
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-07-09 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 1:37 [PATCH 0/1] *** SUBJECT HERE *** Peter Seebach
2012-07-04 1:37 ` [PATCH 1/1] pseudo: Update to 1.3.1 (fixing chroot crash) Peter Seebach
2012-07-09 16:51 ` Saul Wold [this message]
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=4FFB0C2C.2080003@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