From: Adrian Bunk <bunk@stusta.de>
To: bruce.ashfield@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/8] kernel-devsrc: remove python2 dependency
Date: Wed, 28 Aug 2019 23:05:36 +0300 [thread overview]
Message-ID: <20190828200536.GD3044@localhost> (raw)
In-Reply-To: <4f7fa357480ec0139aa809bed4a12c9aa7622d60.1567019771.git.bruce.ashfield@gmail.com>
On Wed, Aug 28, 2019 at 03:28:38PM -0400, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Witht the approaching EOL of python2, the kernel packages need to
> be updated to depend on python3.
>...
Yocto 3.0 ships and supports Python 2.7, so there is no urgent need for
last-minute Python 2 -> 3 changes.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-08-28 20:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 19:28 [PATCH 0/8] kernel/kernel-yocto: consolidated M3 feature pull request bruce.ashfield
2019-08-28 19:28 ` [PATCH 1/8] linux-libc-headers: update to v5.2 headers bruce.ashfield
2019-08-28 19:28 ` [PATCH 2/8] linux-yocto: introduce 5.2 recipes bruce.ashfield
2019-08-28 20:00 ` Adrian Bunk
2019-08-28 20:06 ` Bruce Ashfield
2019-08-28 19:28 ` [PATCH 3/8] bluez5: fix build against libc-headers 5.2+ bruce.ashfield
2019-08-28 19:28 ` [PATCH 4/8] kernel-devsrc: remove python2 dependency bruce.ashfield
2019-08-28 20:05 ` Adrian Bunk [this message]
2019-08-28 20:11 ` Bruce Ashfield
2019-08-28 21:58 ` Adrian Bunk
2019-08-28 22:06 ` Bruce Ashfield
2019-08-29 6:31 ` Adrian Bunk
2019-08-29 12:23 ` Bruce Ashfield
2019-08-29 12:53 ` Adrian Bunk
2019-08-29 13:00 ` Alexander Kanavin
2019-08-28 20:12 ` richard.purdie
2019-08-28 20:57 ` Alexander Kanavin
2019-08-28 19:28 ` [PATCH 5/8] perf: change dependencies on python to python3 bruce.ashfield
2019-08-29 0:01 ` Mittal, Anuj
2019-08-29 0:13 ` Bruce Ashfield
2019-08-29 0:18 ` Mittal, Anuj
2019-08-29 0:24 ` Bruce Ashfield
2019-08-29 0:27 ` Bruce Ashfield
2019-08-29 1:08 ` Bruce Ashfield
2019-08-28 19:28 ` [PATCH 6/8] perf: v5.3+ build fixes bruce.ashfield
2019-08-29 0:32 ` Bruce Ashfield
2019-08-29 1:45 ` Bruce Ashfield
2019-08-28 19:28 ` [PATCH 7/8] devsrc: update arm64 scripts/prepare for kernels 5.3+ bruce.ashfield
2019-08-28 19:28 ` [PATCH 8/8] qemu: bump linux-yocto preferred version to 5.2 bruce.ashfield
2019-08-28 19:33 ` ✗ patchtest: failure for kernel/kernel-yocto: consolidated M3 feature pull request 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=20190828200536.GD3044@localhost \
--to=bunk@stusta.de \
--cc=bruce.ashfield@gmail.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