From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Paul Barker" <paul@pbarker.dev>, <yocto@lists.yoctoproject.org>,
<openembedded-core@lists.openembedded.org>,
<yocto-status@lists.yoctoproject.org>
Subject: Re: [OE-core] Yocto Project Status 10 February 2026 (WW07)
Date: Tue, 10 Feb 2026 16:55:00 +0100 [thread overview]
Message-ID: <DGBEJWQD2JEH.3TTL8JP14XJG7@bootlin.com> (raw)
In-Reply-To: <19266426506120e17fec17b1eeb1ed03ee36d8ec.camel@pbarker.dev>
Hi,
On Tue Feb 10, 2026 at 4:50 PM CET, Paul Barker wrote:
[...]
> - Patch review is now using two branches:
> - “master-review” - patches which pass on the autobuilder and will
> be discussed on the patch review call
> (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
> - “master-backlog” - patches which have been discussed and need
> further investigation or more detailed feedback which we haven’t
> had time for yet
> (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
Do we want this documented on docs.yoctoproject.org?
Also, what becomes of master-next?
Thanks,
Antonin
prev parent reply other threads:[~2026-02-10 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 15:50 Yocto Project Status 10 February 2026 (WW07) Paul Barker
2026-02-10 15:55 ` Antonin Godard [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=DGBEJWQD2JEH.3TTL8JP14XJG7@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
--cc=yocto-status@lists.yoctoproject.org \
--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