From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Martin Jansa <Martin.Jansa@gmail.com>
Cc: Tim Orling <ticotimo@gmail.com>,
Yocto-mailing-list <yocto@lists.yoctoproject.org>,
openembedded-core <openembedded-core@lists.openembedded.org>,
"openembedded-devel@lists.openembedded.org"
<Openembedded-devel@lists.openembedded.org>,
Anibal Limon <anibal.limon@linaro.org>
Subject: Re: [yocto] [OE-core] Let me tell you how I really feel. Zero filter. If you need meta-python2, you need to become a maintainer. Immediately. Period.
Date: Tue, 02 Feb 2021 09:33:03 +0000 [thread overview]
Message-ID: <456f2eb44ad30da1e4422d06267c07e7c57595aa.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQeJnDzgusQvqEWkkNwkoDxR1fMhrb0kM3932D71yWTMRw@mail.gmail.com>
On Mon, 2021-02-01 at 15:40 +0100, Martin Jansa wrote:
> can I get the write access to meta-python2 as mentioned above?
>
> I have 2 fixes to make it parse able with latest oe-core:
> https://lists.openembedded.org/g/openembedded-devel/message/89201
> https://lists.openembedded.org/g/openembedded-devel/message/89200
>
> to fix issues discussed in:
> https://github.com/openembedded/openembedded-core/commit/fd6a007efa7cb45101a66f294af81d9d33bb3fab#commitcomment-46565284
> https://lists.openembedded.org/g/openembedded-core/message/147477
> https://lists.openembedded.org/g/openembedded-core/message/147514
This sounds like a good idea to me and I have admin right so I've given
you access :)
Cheers,
Richard
next prev parent reply other threads:[~2021-02-02 9:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 0:48 Let me tell you how I really feel. Zero filter. If you need meta-python2, you need to become a maintainer. Immediately. Period Tim Orling
2020-10-22 21:36 ` [OE-core] " Martin Jansa
2020-10-22 21:39 ` [yocto] " Khem Raj
2020-10-24 10:53 ` [yocto] " Zoran
2020-10-24 11:19 ` Alexander Kanavin
[not found] ` <1640E842B1461A14.10923@lists.yoctoproject.org>
2020-10-24 17:38 ` Zoran
2020-10-24 20:22 ` Alexander Kanavin
2020-10-24 20:26 ` Zoran
2020-10-24 20:29 ` Alexander Kanavin
2020-10-24 21:51 ` [oe] " Alejandro Hernandez Samaniego
[not found] ` <16406E32EA0586FD.712@lists.yoctoproject.org>
2021-02-01 14:40 ` [yocto] [OE-core] " Martin Jansa
2021-02-01 23:19 ` Khem Raj
2021-02-02 9:33 ` Richard Purdie [this message]
2021-02-02 10:11 ` Zoran
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=456f2eb44ad30da1e4422d06267c07e7c57595aa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Martin.Jansa@gmail.com \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=anibal.limon@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ticotimo@gmail.com \
--cc=yocto@lists.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