All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/4] Progress fixes
Date: Thu, 11 Aug 2016 15:36:56 +1200	[thread overview]
Message-ID: <cover.1470886482.git.paul.eggleton@linux.intel.com> (raw)

Fixes for minor issues in the progress bar display, plus a patch for
some unclosed files that I noticed at the same time as working on these.


The following changes since commit 0a9b5d7d9655dbb09d458fc6e330e932f0f9dab6:

  toaster: buildinfohelper Add handling local layers (i.e. non-git) layers (2016-08-11 00:08:18 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib paule/bb-progress-fixes2
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bb-progress-fixes2

Paul Eggleton (4):
  runqueue: fix two minor issues with the initialising tasks progress
  knotty: fix task progress bar not starting at 0%
  knotty: don't show number of running tasks in quiet mode
  siggen: properly close files rather than opening them inline

 lib/bb/runqueue.py  |  5 +++--
 lib/bb/siggen.py    | 15 +++++++++------
 lib/bb/ui/knotty.py | 11 ++++++++---
 3 files changed, 20 insertions(+), 11 deletions(-)

-- 
2.5.5



             reply	other threads:[~2016-08-11  3:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11  3:36 Paul Eggleton [this message]
2016-08-11  3:36 ` [PATCH 1/4] runqueue: fix two minor issues with the initialising tasks progress Paul Eggleton
2016-08-11  3:36 ` [PATCH 2/4] knotty: fix task progress bar not starting at 0% Paul Eggleton
2016-08-11  3:36 ` [PATCH 3/4] knotty: don't show number of running tasks in quiet mode Paul Eggleton
2016-08-11  3:37 ` [PATCH 4/4] siggen: properly close files rather than opening them inline Paul Eggleton
2016-08-16 21:16   ` Peter Kjellerstedt
2016-08-16 22:30     ` Paul Eggleton

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.1470886482.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.