From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [PATCH] [OE-core] [PATCH] ninja: upgrade 1.10.2 -> 1.11.0
Date: Tue, 24 May 2022 16:33:45 +0800 [thread overview]
Message-ID: <1653381225-6080-4-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1653381225-6080-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../recipes-devtools/ninja/{ninja_1.10.2.bb => ninja_1.11.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/ninja/{ninja_1.10.2.bb => ninja_1.11.0.bb} (94%)
diff --git a/meta/recipes-devtools/ninja/ninja_1.10.2.bb b/meta/recipes-devtools/ninja/ninja_1.11.0.bb
similarity index 94%
rename from meta/recipes-devtools/ninja/ninja_1.10.2.bb
rename to meta/recipes-devtools/ninja/ninja_1.11.0.bb
index 7270321d6e..4ec361cc1a 100644
--- a/meta/recipes-devtools/ninja/ninja_1.10.2.bb
+++ b/meta/recipes-devtools/ninja/ninja_1.11.0.bb
@@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=a81586a64ad4e476c791cda7e2f2c52e"
DEPENDS = "re2c-native ninja-native"
-SRCREV = "e72d1d581c945c158ed68d9bc48911063022a2c6"
+SRCREV = "51edeeb063a82693573db43782d9e3733b2840e4"
SRC_URI = "git://github.com/ninja-build/ninja.git;branch=release;protocol=https"
UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.*)"
--
2.25.1
next prev parent reply other threads:[~2022-05-24 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 8:33 [PATCH] [OE-core] [PATCH] bind: upgrade 9.18.2 -> 9.18.3 Wang Mingyu
2022-05-24 8:33 ` [PATCH] [OE-core] [PATCH] ccache: upgrade 4.6 -> 4.6.1 Wang Mingyu
2022-05-24 8:33 ` [PATCH] [OE-core] [PATCH] init-system-helpers: upgrade 1.62 -> 1.63 Wang Mingyu
2022-05-24 8:33 ` Wang Mingyu [this message]
2022-07-18 6:42 ` [PATCH] [OE-core] [PATCH] bind: upgrade 9.18.2 -> 9.18.3 Yi Zhao
2022-07-18 14:45 ` Steve Sakoman
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=1653381225-6080-4-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.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