From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] repo: upgrade 2.25 -> 2.26
Date: Mon, 30 May 2022 14:40:50 +0800 [thread overview]
Message-ID: <1653892850-23554-4-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1653892850-23554-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
meta/recipes-devtools/repo/{repo_2.25.bb => repo_2.26.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/repo/{repo_2.25.bb => repo_2.26.bb} (95%)
diff --git a/meta/recipes-devtools/repo/repo_2.25.bb b/meta/recipes-devtools/repo/repo_2.26.bb
similarity index 95%
rename from meta/recipes-devtools/repo/repo_2.25.bb
rename to meta/recipes-devtools/repo/repo_2.26.bb
index b7332515c8..ff5b7eb6aa 100644
--- a/meta/recipes-devtools/repo/repo_2.25.bb
+++ b/meta/recipes-devtools/repo/repo_2.26.bb
@@ -12,7 +12,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
SRC_URI = "git://gerrit.googlesource.com/git-repo.git;protocol=https;branch=main \
file://0001-python3-shebang.patch \
"
-SRCREV = "501733c2abb1180679f25b2f78970d73a2f8d413"
+SRCREV = "bdcba7dc36f1c8e6041681eb5b3b5229c93c7c5c"
MIRRORS += "git://gerrit.googlesource.com/git-repo.git git://github.com/GerritCodeReview/git-repo.git"
--
2.25.1
prev parent reply other threads:[~2022-05-30 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 6:40 [OE-core] [PATCH] logrotate: upgrade 3.19.0 -> 3.20.1 Wang Mingyu
2022-05-30 6:40 ` [OE-core] [PATCH] btrfs-tools: upgrade 5.16.2 -> 5.18 Wang Mingyu
2022-05-30 20:48 ` Luca Ceresoli
2022-05-30 6:40 ` [OE-core] [PATCH] dpkg: upgrade 1.21.7 -> 1.21.8 Wang Mingyu
2022-05-30 6:40 ` Wang Mingyu [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=1653892850-23554-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