From: bavery <brian.avery@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] toaster: Better SDK artifacts and fstypes V2
Date: Tue, 12 Jul 2016 15:54:26 -0700 [thread overview]
Message-ID: <cover.1468363460.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 is a second version of the patch.
These patches remove complexity from the toaster.bbclass in order to move those
functions to bitbake/lib/toaster.
The overall intent of this set is to improve Toaster's ability to locate artifacts,
specify fstypes correctly, and add some tests for these changes.
-brian avery
an Intel employee
The following changes since commit 0659b4f780120b1459b068c85794be4f04f943bd:
toaster: fix typo in arguments for libtoaster.js function (2016-07-12 14:12:16 -0700)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib bavery/submit/elliot/toaster/8556-image_fstypesV2_foroe
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/submit/elliot/toaster/8556-image_fstypesV2_foroe
Elliot Smith (2):
toaster.bbclass: remove directory scan logic for detecting artifacts
toaster.bbclass: only scan files-in-image.txt if it exists
classes/toaster.bbclass | 99 ++++++++++++-------------------------------------
1 file changed, 24 insertions(+), 75 deletions(-)
--
1.9.1
next reply other threads:[~2016-07-12 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 22:54 bavery [this message]
2016-07-12 22:54 ` [PATCH 1/2] toaster.bbclass: remove directory scan logic for detecting artifacts bavery
2016-07-12 22:54 ` [PATCH 2/2] toaster.bbclass: only scan files-in-image.txt if it exists bavery
2016-07-19 8:04 ` [PATCH 0/2] toaster: Better SDK artifacts and fstypes V2 Richard Purdie
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.1468363460.git.brian.avery@intel.com \
--to=brian.avery@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