From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/3] devpyshell fixes
Date: Tue, 5 Jul 2016 01:08:12 +0300 [thread overview]
Message-ID: <cover.1467669922.git.ed.bartosh@linux.intel.com> (raw)
Hi,
This patchset fixes several devpyshell bugs caused by moving to Python 3.
Please, note that it contains fix for double unbuffering, which was sent in
a separate patchset targeting jethro, krogoth and master. It's included here
just to keep it together with the rest of devpyshell fixes for master.
Changes in v2: removed bitbake patch from the series
The following changes since commit 5c11e365e19357f721c49d076971567e7b64b61b:
lib/oeqa: add Galculator to SDK and runtime tests (2016-07-01 16:22:48 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ed/oe-core/devpyshell-python3
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/oe-core/devpyshell-python3
Ed Bartosh (3):
devshell.bbclass: fix double unbuffering
devpyshell: python3: flush stdout explicitly
oepydevshell-internal: python3: encode/decode pty content
meta/classes/devshell.bbclass | 5 ++---
scripts/oepydevshell-internal.py | 12 +++++-------
2 files changed, 7 insertions(+), 10 deletions(-)
--
Regards,
Ed
next reply other threads:[~2016-07-04 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 22:08 Ed Bartosh [this message]
2016-07-04 22:08 ` [PATCH v2 1/3] devshell.bbclass: fix double unbuffering Ed Bartosh
2016-07-04 22:08 ` [PATCH v2 2/3] devpyshell: python3: flush stdout explicitly Ed Bartosh
2016-07-04 22:08 ` [PATCH v2 3/3] oepydevshell-internal: python3: encode/decode pty content Ed Bartosh
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.1467669922.git.ed.bartosh@linux.intel.com \
--to=ed.bartosh@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