From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Scott Rifenbark <srifenbark@gmail.com>
Cc: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [yocto] 2.6 migration guide
Date: Fri, 09 Nov 2018 11:50:01 +1300 [thread overview]
Message-ID: <1625935.REkM3HMYJn@localhost.localdomain> (raw)
In-Reply-To: <6194709.vnUpm0U1CA@localhost.localdomain>
On Friday, 9 November 2018 11:41:42 AM NZDT Paul Eggleton wrote:
> You could accomplish the latter using PACKAGECONFIG_pn-python3 = "pgo" at
> the configuration level
Oops, I meant PACKAGECONFIG_remove_pn-python3 = "pgo" here.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2018-11-08 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 21:14 2.6 migration guide Paul Eggleton
2018-10-30 22:06 ` Scott Rifenbark
[not found] ` <25f056c7-d6ba-499f-8bf4-b8d1470fff4b@gmail.com>
2018-10-31 15:33 ` [yocto] " Scott Rifenbark
2018-10-31 15:50 ` Scott Rifenbark
2018-10-31 16:01 ` Bas Mevissen
2018-10-31 16:56 ` Scott Rifenbark
2018-11-02 15:10 ` Peter Kjellerstedt
2018-11-02 15:48 ` Scott Rifenbark
2018-11-05 3:32 ` Paul Eggleton
2018-11-08 22:41 ` [yocto] " Paul Eggleton
2018-11-08 22:50 ` Paul Eggleton [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=1625935.REkM3HMYJn@localhost.localdomain \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=srifenbark@gmail.com \
--cc=yocto@yoctoproject.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