Yocto Project Discussions
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: yocto@lists.yoctoproject.org, nguyenthaithuanalg@gmail.com,
	Gyorgy Sarvari <skandigraun@gmail.com>
Subject: Re: [yocto] A new member
Date: Fri, 11 Apr 2025 14:16:29 +0200	[thread overview]
Message-ID: <60792f52-b330-43a4-bb62-bef2b0be5845@cherry.de> (raw)
In-Reply-To: <2395.1744373336201661750@lists.yoctoproject.org>

Hi,

On 4/11/25 2:08 PM, Thuận Nguyễn-Thái via lists.yoctoproject.org wrote:
> You don't often get email from nguyenthaithuanalg=gmail.com@lists.yoctoproject.org. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
> Hi Gyorgy,
> Let me paraphrase your hints by the steps below:
> 1. I fork a new one from "master" as: https://github.com/thuanalg/poky

No, as

https://github.com/thuanalg/meta-openembedded

poky is not meta-openembedded, don't mix both.

Similarly, poky is not openembedded-core (often shortened to OE-Core).

> 2. Add my new recipe into "meta-openembedded"

So far so good. It'll need to be in one of the "sub"layers, whatever is 
the most appropriate for your recipe. Cannot tell you what that would be.

You could also have your own layer in your own git repository as 
Alexander just suggested in another mail.

> 3. Send mail to the Admin about my recipe. If that which email? Khem Raj raj.khem@gmail.com?<mailto:raj.khem@gmail.com>

Then you follow the instructions from the README inside the layer.

The same set of rules for mailing list contribution as for poky/oe-core 
is likely to apply to this git repo, so follow 
https://docs.yoctoproject.org/contributor-guide/submit-changes.html 
(4.5.3 can be skipped).

You probably want to have a look at 
https://docs.yoctoproject.org/contributor-guide/recipe-style-guide.html too.

Cheers,
Quentin


      parent reply	other threads:[~2025-04-11 12:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09  9:58 A new member Thuận Nguyễn-Thái
2025-04-09 11:08 ` [yocto] " Gyorgy Sarvari
2025-04-09 13:52   ` Thuận Nguyễn-Thái
2025-04-09 14:40     ` Gyorgy Sarvari
2025-04-09 17:06       ` Thuận Nguyễn-Thái
2025-04-09 17:20         ` Gyorgy Sarvari
2025-04-11 10:52           ` Thuận Nguyễn-Thái
2025-04-11 11:48             ` Gyorgy Sarvari
2025-04-11 12:08               ` Thuận Nguyễn-Thái
2025-04-11 12:15                 ` Alexander Kanavin
2025-04-11 12:18                   ` Thuận Nguyễn-Thái
2025-04-11 12:46                     ` Alexander Kanavin
2025-04-12  3:28                       ` Thuận Nguyễn-Thái
2025-04-12  6:57                         ` Gyorgy Sarvari
2025-04-12  7:31                           ` Thuận Nguyễn-Thái
2025-04-12 16:08                             ` Thuận Nguyễn-Thái
2025-04-12 16:58                               ` Gyorgy Sarvari
2025-04-12 17:49                                 ` Thuận Nguyễn-Thái
2025-05-03 16:37                                 ` Thuận Nguyễn-Thái
2025-05-03 17:35                                   ` Gyorgy Sarvari
2025-04-12 16:09                           ` Thuận Nguyễn-Thái
2025-04-11 12:16                 ` 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=60792f52-b330-43a4-bb62-bef2b0be5845@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=nguyenthaithuanalg@gmail.com \
    --cc=skandigraun@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