From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/1] Clear Knotty footer before outputting to stderr
Date: Tue, 8 Apr 2014 16:09:33 +0200 [thread overview]
Message-ID: <cover.1396966113.git.pkj@axis.com> (raw)
This fixes a problem with Knotty when errors are output to stderr
while the footer of currently active tasks is displayed.
//Peter
The following changes since commit 68a55c8ff779d8df90626e68d5d4e48660dd8027:
ref-manual: Edits to fix up how GID and UIDs are handled. (2014-04-08 14:20:16 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib pkj/knotty_stderr
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/knotty_stderr
Peter Kjellerstedt (1):
bitbake: knotty: Clear footer before outputting to stderr
bitbake/lib/bb/ui/knotty.py | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
1.9.0
next reply other threads:[~2014-04-08 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 14:09 Peter Kjellerstedt [this message]
2014-04-08 14:09 ` [PATCH 1/1] bitbake: knotty: Clear footer before outputting to stderr Peter Kjellerstedt
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.1396966113.git.pkj@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=bitbake-devel@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