From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Alexander Kanavin" <alex.kanavin@gmail.com>
Cc: "OE-core ML" <openembedded-core@lists.openembedded.org>,
<mark.hatle@amd.com>
Subject: Re: [OE-core] [PATCH] pseudo: inherit upstream-stable-release-point
Date: Wed, 18 Nov 2026 10:04:42 +0100 [thread overview]
Message-ID: <DMY7SUIMH84V.3DI26DWHENG5F@smile.fr> (raw)
In-Reply-To: <CANNYZj9Uj5v-Tb1TrA+TrxrdEyjO+qj25byZ0fWtUpiLHKH-DA@mail.gmail.com>
On Tue Nov 17, 2026 at 6:13 PM CET, Alexander Kanavin wrote:
> On Tue, 17 Nov 2026 at 17:42, Yoann Congal via openembedded-core
> <yoann.congal=smile.fr@lists.openembedded.org> wrote:
>
>>
>> Pseudo now has a stable branch pseudo-1.9 with pseudo-1.9.x tags on it.
>
>
> Is this branch collecting only bugfixes (or fixes needed for continuing
> operation of yocto release branches)? Is this going to be a policy for any
> future point releases, or is it a one-off just for 1.9.x? There should be
> confirmation of these questions, in addition to the existence of the branch.
>
> Alex
Hello,
Good point.
The best we have right now is this:
https://lore.kernel.org/all/1783104055-19005-1-git-send-email-mark.hatle@kernel.crashing.org/
> (I have already created a pseudo-1.9 branch so we can backport stable
> changes as needed.)
Which is a bit terse...
As nothing about this is urgent nor critical, I've created a bug:
16529 – Document pseudo stable policy (1.9.x)
https://bugzilla.yoctoproject.org/show_bug.cgi?id=16529
... so it can be treated at the right time.
As for this patch, let's hold it until the policy has been cleared up.
Regards,
--
Yoann Congal
Smile ECS
prev parent reply other threads:[~2026-11-18 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 16:41 [PATCH] pseudo: inherit upstream-stable-release-point Yoann Congal
2026-11-17 17:13 ` [OE-core] " Alexander Kanavin
2026-11-18 9:04 ` Yoann Congal [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=DMY7SUIMH84V.3DI26DWHENG5F@smile.fr \
--to=yoann.congal@smile.fr \
--cc=alex.kanavin@gmail.com \
--cc=mark.hatle@amd.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