From: David Partain <david.partain@est.tech>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Daniel Turull <daniel.turull@ericsson.com>,
"elin-upstream@mailman.lmera.ericsson.se"
<elin-upstream@mailman.lmera.ericsson.se>
Cc: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"paul@pbarker.dev" <paul@pbarker.dev>,
"alex.kanavin@gmail.com" <alex.kanavin@gmail.com>,
"Randy.MacLeod@windriver.com" <Randy.MacLeod@windriver.com>
Subject: Re: [ELIN-upstream] [PATCH 0/7] Mark recipes whose point releases are fixes-only (2/3)
Date: Tue, 4 Aug 2026 14:40:31 +0000 [thread overview]
Message-ID: <dc83efc3a1190f4f79ae4bb19156bd6b35e38497.camel@est.tech> (raw)
In-Reply-To: <20260804141135.3779287-1-daniel.turull@ericsson.com>
On Tue, 2026-08-04 at 16:11 +0200, daniel.turull@ericsson.com wrote:
> From: Daniel Turull <daniel.turull@ericsson.com>
>
> Second of three series opting recipes into UPSTREAM_STABLE_RELEASE_REGEX. The
> first covered recipes whose upstream publishes a written stable-branch policy
> and
> is in master-next. This one covers recipes with no such document, qualifying
> instead on branch structure and changelog evidence; the third will cover
> smaller
> components with weaker evidence.
These all look good to me.
David
prev parent reply other threads:[~2026-08-04 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 14:11 [PATCH 0/7] Mark recipes whose point releases are fixes-only (2/3) daniel.turull
2026-08-04 14:11 ` [PATCH 1/7] libxml2: inherit upstream-stable-release-point daniel.turull
2026-08-04 14:11 ` [PATCH 2/7] python3: " daniel.turull
2026-08-04 14:11 ` [PATCH 3/7] openssl: " daniel.turull
2026-08-04 14:11 ` [PATCH 4/7] binutils: " daniel.turull
2026-08-04 14:11 ` [PATCH 5/7] libgcrypt: " daniel.turull
2026-08-04 14:11 ` [PATCH 6/7] sqlite3: " daniel.turull
2026-08-04 14:11 ` [PATCH 7/7] lttng-tools: " daniel.turull
2026-08-04 14:40 ` David Partain [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=dc83efc3a1190f4f79ae4bb19156bd6b35e38497.camel@est.tech \
--to=david.partain@est.tech \
--cc=Randy.MacLeod@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=daniel.turull@ericsson.com \
--cc=elin-upstream@mailman.lmera.ericsson.se \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.