From: "Khem Raj" <raj.khem@gmail.com>
To: Adrian Bunk <bunk@stusta.de>, Martin Jansa <martin.jansa@gmail.com>
Cc: Andrey Zhizhikin <andrey.z@gmail.com>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Steve Sakoman <sakoman@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Denys Dmytriyenko <denis@denix.org>,
Joshua Watt <jpewhacker@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
"jdmason@kudzu.us" <jdmason@kudzu.us>
Subject: Re: [OE-core][PATCH 0/4] Import recipes from meta-python
Date: Sun, 17 May 2020 16:47:13 -0700 [thread overview]
Message-ID: <5731941e-fe0c-e242-bea5-cd0d3c2ef772@gmail.com> (raw)
In-Reply-To: <20200517161441.GB16162@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 647 bytes --]
On 5/17/20 9:14 AM, Adrian Bunk wrote:
> On Sun, May 17, 2020 at 06:00:58PM +0200, Martin Jansa wrote:
>> ...
>> But IMHO carrying duplicate recipes in oe-core and meta-oe, just because
>> some users aren't updating meta-oe, only adds more confusion.
>> ...
>
> IMHO moving recipes from meta-openembedded (or other layers) to oe-core
> in a released stable series is not a good idea.
I think in current form in this situation it certainly seems a bit
complex sadly, however, we also need to explore if there is some "good"
way of doing such changes without breaking distro builders.
>
>> Cheers,
>
> cu
> Adrian
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2020-05-17 23:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 21:04 [OE-core][PATCH 0/4] Import recipes from meta-python Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 1/4] pycryptodome: Import " Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 2/4] pyelftools: " Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 3/4] python3-pycryptodome(x): Upgrade 3.9.4 -> 3.9.7 Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 4/4] python3-pyelftools: Upgrade 0.25 -> 0.26 Joshua Watt
2020-05-15 18:53 ` [OE-core][PATCH 0/4] Import recipes from meta-python Denys Dmytriyenko
2020-05-15 19:05 ` Richard Purdie
2020-05-15 19:12 ` Joshua Watt
2020-05-15 19:26 ` Denys Dmytriyenko
2020-05-15 19:56 ` Andrey Zhizhikin
2020-05-15 19:32 ` Khem Raj
2020-05-17 1:05 ` Alejandro Hernandez
2020-05-16 1:21 ` Steve Sakoman
2020-05-16 17:47 ` Adrian Bunk
2020-05-16 19:54 ` Peter Kjellerstedt
2020-05-16 20:09 ` Adrian Bunk
2020-05-16 20:24 ` Andrey Zhizhikin
2020-05-16 23:15 ` Andre McCurdy
2020-05-17 13:22 ` Adrian Bunk
2020-05-17 13:56 ` Martin Jansa
2020-05-17 15:45 ` Adrian Bunk
2020-05-17 16:00 ` Martin Jansa
2020-05-17 16:14 ` Adrian Bunk
2020-05-17 23:47 ` Khem Raj [this message]
2020-05-19 18:20 ` Steve Sakoman
2020-05-19 18:24 ` Martin Jansa
2020-05-19 19:57 ` Andre McCurdy
2020-05-21 9:11 ` Martin Jansa
2020-05-17 23:45 ` Khem Raj
2020-05-17 23:41 ` Khem Raj
2020-05-18 6:41 ` Alejandro Hernandez
2020-05-17 23:38 ` Khem Raj
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=5731941e-fe0c-e242-bea5-cd0d3c2ef772@gmail.com \
--to=raj.khem@gmail.com \
--cc=andrey.z@gmail.com \
--cc=bunk@stusta.de \
--cc=denis@denix.org \
--cc=jdmason@kudzu.us \
--cc=jpewhacker@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=sakoman@gmail.com \
/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