From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Yoann Congal" <yoann.congal@smile.fr>,
"Marko, Peter" <Peter.Marko@siemens.com>,
"careers.myinfo@gmail.com" <careers.myinfo@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][scarthgap][PATCH 1/2] libpcre2: Enable Ptest Support
Date: Fri, 06 Mar 2026 19:52:39 +0100 [thread overview]
Message-ID: <DGVXD029L9TG.2EMNRFUGNCBVF@smile.fr> (raw)
In-Reply-To: <DGJ0I1AYCUMK.2QUHJL111LVBU@smile.fr>
On Thu Feb 19, 2026 at 3:35 PM CET, Yoann Congal wrote:
> On Wed Feb 18, 2026 at 9:16 AM CET, Peter Marko wrote:
>> Could we add "adding/improving tests" to the allowed LTS backport items?
>> I think we're shooting ourselves in the foot here.
>
> FYI, I've asked the Yocto Project TSC about this.
Hello,
I'm sorry but we decided that standalone tests like this one are not
acceptable for stable inclusion.
For more detail, see "Clarification on ptest/selftest backports for stable branches"
https://lore.kernel.org/openembedded-core/DGVX4XQ6VLWT.1HOMXA78ZXLBG@smile.fr/T/#u
Regards,
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-03-06 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 7:23 [OE-core][scarthgap][PATCH 1/2] libpcre2: Enable Ptest Support Shaik Moin
2026-02-11 7:23 ` [OE-core][scarthgap][PATCH 2/2] libpcre2: fix RunGrepTest Failure on Busybox systems Shaik Moin
2026-02-11 8:53 ` [OE-core][scarthgap][PATCH 1/2] libpcre2: Enable Ptest Support Yoann Congal
2026-02-18 5:30 ` Shaik Moin
2026-02-18 8:01 ` Yoann Congal
2026-02-18 8:16 ` Marko, Peter
2026-02-19 14:35 ` Yoann Congal
2026-02-20 6:29 ` Shaik Moin
2026-03-06 18:52 ` Yoann Congal [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-20 7:36 Shaik Moin
2026-02-08 23:30 ` Yoann Congal
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=DGVXD029L9TG.2EMNRFUGNCBVF@smile.fr \
--to=yoann.congal@smile.fr \
--cc=Peter.Marko@siemens.com \
--cc=careers.myinfo@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