Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Alper Ak" <alperyasinak1@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v5 0/7] cmake: Major version bump to 4.0.3
Date: Mon, 07 Jul 2025 10:55:33 -0700	[thread overview]
Message-ID: <28216.1751910933329662196@lists.openembedded.org> (raw)
In-Reply-To: <CAMKF1sr80kZEZunuw4mo32TbKXdrGUb853J8sA3EHuvc8suN3g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 582 bytes --]

Hi everyone,

I have started fixing recipes in meta-openembedded, but I'm not sure how we can prevent multiple people from working on the same recipe at the same time. Since it's likely that others will also start fixing recipes, maybe we need a way to coordinate or reserve recipes to avoid duplicate efforts. Otherwise, there’s a chance that two people could start fixing the same recipe without knowing about each other’s work.

Is there any recommended way to coordinate, or maybe we could create a list or use issues to "claim" a recipe before starting to work on it?

[-- Attachment #2: Type: text/html, Size: 639 bytes --]

  reply	other threads:[~2025-07-07 17:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 13:27 [PATCH v5 0/7] cmake: Major version bump to 4.0.3 Moritz Haase
2025-07-03 13:27 ` [PATCH v5 1/7] libcomps: Backport patch to support builds with CMake 4+ Moritz Haase
2025-07-03 13:27 ` [PATCH v5 2/7] createrepo-c: Backport patches " Moritz Haase
2025-07-03 13:27 ` [PATCH v5 3/7] apt: Backport patch " Moritz Haase
2025-07-03 13:27 ` [PATCH v5 4/7] libubootenv: " Moritz Haase
2025-07-03 13:27 ` [PATCH v5] musl-locales: Add " Moritz Haase
2025-07-03 13:27 ` [PATCH v5 6/7] libwpe: " Moritz Haase
2025-07-03 13:27 ` [PATCH v5 7/7] cmake: upgrade 3.31.6 -> 4.0.3 Moritz Haase
2025-07-03 13:49   ` Patchtest results for " patchtest
2025-07-04 10:42     ` Haase Moritz, JD-62
2025-07-07 16:53 ` [OE-core] [PATCH v5 0/7] cmake: Major version bump to 4.0.3 Khem Raj
2025-07-07 17:55   ` Alper Ak [this message]
2025-07-08  5:45   ` Haase Moritz, JD-62
2025-07-08  6:08     ` Khem Raj
2025-07-08 13:13     ` Alper Ak
2025-07-10  6:34       ` [OE-core] " Haase Moritz, JD-62
2025-07-10 17:40         ` Khem Raj
2025-07-10 19:10           ` Alper Ak
2025-07-11  2:10             ` Khem Raj
2025-07-11 10:25               ` Haase Moritz, JD-62
2025-07-12 16:22                 ` Khem Raj
2025-07-13  5:45                   ` Khem Raj
2025-07-14  5:02                     ` Khem Raj
2025-07-14 12:16                       ` Haase Moritz, JD-62
2025-07-14 17:53                         ` 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=28216.1751910933329662196@lists.openembedded.org \
    --to=alperyasinak1@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