Openembedded Core Discussions
 help / color / mirror / Atom feed
From: brian avery <avery.brian@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] toaster: Artifact Selection Improvement
Date: Fri,  8 Jul 2016 17:54:01 -0700	[thread overview]
Message-ID: <cover.1468023361.git.brian.avery@intel.com> (raw)

This is part of a patch set that is split over the openembedded-core and
bitbake-devel mailing lists.

This patch removes complexity from toaster.bbclass in order to move those
functions to bitbake/lib/toaster.

The intent of this set is to improve Toaster's ability to locate artifacts such as
kernel images, rootfs, and sdk tar files.

-Brian Avery
an Intel employee

The following changes since commit 308d0a8f1d06b22a9be8e5d55194544a2ee764ef:

  toaster: fix typo in arguments for libtoaster.js function (2016-07-08 16:25:39 -0700)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib poky-contrib/bavery/submit/elliot/toaster/8556-image_fstypes
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/submit/elliot/toaster/8556-image_fstypes

Elliot Smith (1):
  toaster.bbclass: remove directory scan logic for detecting artifacts

 classes/toaster.bbclass | 74 ++++++-------------------------------------------
 1 file changed, 8 insertions(+), 66 deletions(-)

--
1.9.1


             reply	other threads:[~2016-07-09  0:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09  0:54 brian avery [this message]
2016-07-09  0:54 ` [PATCH 1/1] toaster.bbclass: remove directory scan logic for detecting artifacts 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.1468023361.git.brian.avery@intel.com \
    --to=avery.brian@gmail.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