From: Joshua Watt <jpewhacker@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] classes/testsdk: Split implementation into classes
Date: Mon, 19 Nov 2018 10:33:30 -0600 [thread overview]
Message-ID: <4ca98c687b24ace8bd7987455c8aebe0967dce93.camel@gmail.com> (raw)
In-Reply-To: <895f07363a38c1be4c3d584547fffe6e8bc7b0a3.camel@linuxfoundation.org>
On Mon, 2018-11-19 at 14:25 +0000, Richard Purdie wrote:
> Thanks for reworking this, it does look a lot better and should stop
> some of the bbclass proliferation we're seeing.
>
> I assume all the code was functionally unchanged in the move?
Correct.
>
> On Sun, 2018-11-18 at 13:19 -0600, Joshua Watt wrote:
> > python () {
> > - if oe.types.boolean(d.getVar("TESTIMAGE_AUTO") or "False"):
> > - bb.build.addtask("testsdk", None, "do_populate_sdk", d)
> > - bb.build.addtask("testsdkext", None,
> > "do_populate_sdk_ext", d)
> > + auto = oe.types.boolean(d.getVar("TESTIMAGE_AUTO") or "False")
> > + bb.build.addtask("testsdk", None, ("",
> > "do_populate_sdk")[auto], d)
> > + bb.build.addtask("testsdkext", None, ("",
> > "do_populate_sdk_ext")[auto], d)
> > }
>
> This doesn't look like an improvement to code readability? :)
It isn't. I will fix it with v3.
>
> Cheers,
>
> Richard
>
>
>
--
Joshua Watt <JPEWhacker@gmail.com>
next prev parent reply other threads:[~2018-11-19 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 19:14 [PATCH] classes/testsdk: Split implementation into classes Joshua Watt
2018-11-15 19:40 ` Richard Purdie
2018-11-15 22:28 ` Joshua Watt
2018-11-15 22:48 ` richard.purdie
2018-11-18 19:19 ` [PATCH v2] " Joshua Watt
2018-11-19 14:25 ` Richard Purdie
2018-11-19 16:33 ` Joshua Watt [this message]
2018-11-19 18:11 ` [PATCH v3] " Joshua Watt
2018-11-18 19:33 ` ✗ patchtest: failure for classes/testsdk: Split implementation into classes (rev2) Patchwork
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=4ca98c687b24ace8bd7987455c8aebe0967dce93.camel@gmail.com \
--to=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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