From: Quentin Schulz <quentin.schulz@cherry.de>
To: ranjitsinh.rathod@kpit.com,
"Openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"Openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Cc: "alex@linutronix.de" <alex@linutronix.de>,
Scott Murray <scott.murray@konsulko.com>
Subject: Re: [OE-core] How to contribute in meta-lts-mixins layer?
Date: Mon, 29 Jul 2024 15:59:45 +0200 [thread overview]
Message-ID: <f93e5b15-e469-459b-bd17-3e5fcb8d8102@cherry.de> (raw)
In-Reply-To: <MA0PR01MB91744DCAA3A1F5313FF521138FB72@MA0PR01MB9174.INDPRD01.PROD.OUTLOOK.COM>
Hi Ranjitsinh,
On 7/29/24 3:52 PM, Ranjitsinh Rathod via lists.openembedded.org wrote:
> You don't often get email from ranjitsinh.rathod=kpit.com@lists.openembedded.org. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
> Hello all,
>
> I want to contribute for the layer meta-lts-mixins for kirkstone/rust branch. Does anyone suggest which email and labels to use to do contribution for this layer? I did not find any specific contribute guide or details in the repository. Any help is appreciated.
>
I think yocto-patches is the appropriate ML?
https://lists.yoctoproject.org/g/yocto-patches/message/8 is a patch for
meta-lts-mixins scarthgap/u-boot branch I think.
Adding the maintainer in Cc, they would/should know :)
Here's to hoping on of your first patch is adding this information to
the different branches' README :)
Cheers,
Quentin
prev parent reply other threads:[~2024-07-29 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 13:52 How to contribute in meta-lts-mixins layer? Ranjitsinh Rathod
2024-07-29 13:59 ` Quentin Schulz [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=f93e5b15-e469-459b-bd17-3e5fcb8d8102@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ranjitsinh.rathod@kpit.com \
--cc=scott.murray@konsulko.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