From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-swupd][PATCH] swupd-image.bbclass: add missing expand arg in getVars
Date: Fri, 17 Feb 2017 08:38:52 +0100 [thread overview]
Message-ID: <1487317132.13854.508.camel@intel.com> (raw)
In-Reply-To: <1487092855-32555-1-git-send-email-aaron.zinghini@seeingmachines.com>
On Tue, 2017-02-14 at 10:20 -0700, Aaron Zinghini wrote:
> Add "True" to d.getVar() to avoid forking a little while longer.
>
> The expand arg has been set to true by default in master branch and breaks compatibility with branches.
Thanks, applied to master-next (not pushed yet). The right mailing list
for future patches is yocto@yoctoproject.org - I had gotten that wrong
when summarizing the patch submission procedure for you.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2017-02-17 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 17:20 [meta-swupd][PATCH] swupd-image.bbclass: add missing expand arg in getVars Aaron Zinghini
2017-02-17 7:38 ` Patrick Ohly [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=1487317132.13854.508.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-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