Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: brian avery <avery.brian@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/3] Read correct cooker log
Date: Fri, 11 Sep 2015 13:57:20 -0700	[thread overview]
Message-ID: <cover.1442004911.git.avery.brian@gmail.com> (raw)

this patch selects the correct cooker log in both analysis and managed mode.

The following changes since commit d4585fa23d56a58c583ee33db067a23177a936b1:

  bsps: update 3.14 SRCREVs (2015-09-09 14:27:57 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib bavery/submit/elliot/20150911_read-correct-cooker-log
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/submit/elliot/20150911_read-correct-cooker-log

Elliot Smith (3):
  toaster: Read correct cooker log path from toasterui
  toaster: Avoid unnecessary local to local copy of cooker log
  toaster: Don't def a function for each call to build_artifact()

 lib/bb/ui/buildinfohelper.py                       |  8 ++--
 lib/bb/ui/toasterui.py                             |  2 +-
 .../management/commands/checksettings.py           | 22 ---------
 .../bldcontrol/management/commands/runbuilds.py    | 24 +---------
 lib/toaster/toastergui/views.py                    | 53 ++++++----------------
 toaster-requirements.txt                           |  1 +
 6 files changed, 23 insertions(+), 87 deletions(-)

-- 
1.9.1



             reply	other threads:[~2015-09-11 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 20:57 brian avery [this message]
2015-09-11 20:57 ` [PATCH 1/3] toaster: Read correct cooker log path from toasterui brian avery
2015-09-11 20:57 ` [PATCH 2/3] toaster: Avoid unnecessary local to local copy of cooker log brian avery
2015-09-11 20:57 ` [PATCH 3/3] toaster: Don't def a function for each call to build_artifact() brian avery

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.1442004911.git.avery.brian@gmail.com \
    --to=avery.brian@gmail.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