From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: brendan.le.foll@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] package.bbclass: Treat .node files same as .so
Date: Tue, 22 Mar 2016 09:41:27 +0000 [thread overview]
Message-ID: <1458639687.20442.38.camel@linuxfoundation.org> (raw)
In-Reply-To: <1458600779-10847-1-git-send-email-brendan.le.foll@intel.com>
On Mon, 2016-03-21 at 22:52 +0000, brendan.le.foll@intel.com wrote:
> (".so" or ".node" in f)
I'm not sure this will do what you expect with python's operator
ordering?
$ python
>>> bar=[1]
>>> 2 or 1 in bar
2
>>> 2 in bar or 1 in bar
True
Cheers,
Richard
prev parent reply other threads:[~2016-03-22 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 22:52 [PATCH] package.bbclass: Treat .node files same as .so brendan.le.foll
2016-03-22 9:41 ` Richard Purdie [this message]
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=1458639687.20442.38.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=brendan.le.foll@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