From: Randy MacLeod <randy.macleod@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
alex.kanavin@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] ninja: upgrade 1.12.1 -> 1.13.0
Date: Thu, 26 Jun 2025 17:35:53 -0400 [thread overview]
Message-ID: <bae7bb60-41e3-462f-9be0-bc8bf6ff044c@windriver.com> (raw)
In-Reply-To: <cf97cef36e9f78904b09bc88599ec2d21456bcb5.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On 2025-06-26 3:11 a.m., Richard Purdie wrote:
> On Thu, 2025-06-26 at 07:13 +0200, Alexander Kanavin via
> lists.openembedded.org wrote:
>> On Thu, 26 Jun 2025 at 02:21, Randy MacLeod via
>> lists.openembedded.org
>> <randy.macleod=windriver.com@lists.openembedded.org> wrote:
>>> -SRCREV = "2daa09ba270b0a43e1929d29b073348aa985dfaa"
>>> +SRCREV = "b4d51f6ed5bed09dd2b70324df0d9cb4ecad2638"
>>>
>>> SRC_URI = "git://github.com/ninja-
>>> build/ninja.git;branch=release;protocol=https"
>> tag=... should be added here at the same time.
Okay, v2 sent.
> FWIW after the patch on the bitbake list, we could just go through and
> update the exiting urls too...
There are ~161 such cases for oe-core:
❯ rg SRC_URI.*git.*branch meta/ | rg -v tag | wc -l
161
and for meta-oe.git:
❯ rg SRC_URI.*git.*branch meta-* | rg -v tag | wc -l
731
and for meta-virt:
❯ rg SRC_URI.*git.*branch | rg -v tag | wc -l
812
It's not easily script-able since everyone has their own tag
prefix/postfix style. Fun!
There's probably a way to get the format of the tag with a bit of
scripting...
I'll likely work on and send these changes for oe-core by recipe-foo
sub-directory
unless I get it fully automated.
../Randy
>
> Cheers,
>
> Richard
--
# Randy MacLeod
# Wind River Linux
[-- Attachment #2: Type: text/html, Size: 2928 bytes --]
prev parent reply other threads:[~2025-06-26 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 0:21 [PATCH] ninja: upgrade 1.12.1 -> 1.13.0 Randy.MacLeod
2025-06-26 5:13 ` [OE-core] " Alexander Kanavin
2025-06-26 7:11 ` Richard Purdie
2025-06-26 21:35 ` Randy MacLeod [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=bae7bb60-41e3-462f-9be0-bc8bf6ff044c@windriver.com \
--to=randy.macleod@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--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.