From: <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] libgit2: upgrade 1.6.3 -> 1.6.4
Date: Mon, 17 Apr 2023 16:04:27 +0800 [thread overview]
Message-ID: <1681718671-19418-1-git-send-email-wangmy@fujitsu.com> (raw)
From: Wang Mingyu <wangmy@fujitsu.com>
Bug fixes
=========
config: return GIT_ENOTFOUND for missing programdata
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../libgit2/{libgit2_1.6.3.bb => libgit2_1.6.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/libgit2/{libgit2_1.6.3.bb => libgit2_1.6.4.bb} (92%)
diff --git a/meta/recipes-support/libgit2/libgit2_1.6.3.bb b/meta/recipes-support/libgit2/libgit2_1.6.4.bb
similarity index 92%
rename from meta/recipes-support/libgit2/libgit2_1.6.3.bb
rename to meta/recipes-support/libgit2/libgit2_1.6.4.bb
index cab7d7a20a..ffe00d8653 100644
--- a/meta/recipes-support/libgit2/libgit2_1.6.3.bb
+++ b/meta/recipes-support/libgit2/libgit2_1.6.4.bb
@@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=5bdf47bbc9a39dc6ce076d59e322dc17"
DEPENDS = "curl openssl zlib libssh2 libgcrypt libpcre2"
SRC_URI = "git://github.com/libgit2/libgit2.git;branch=maint/v1.6;protocol=https"
-SRCREV = "c058aa87dce4c67a3b86b3349beebd64b7bedcd3"
+SRCREV = "e6325351ceee58cf56f58bdce61b38907805544f"
S = "${WORKDIR}/git"
--
2.34.1
next reply other threads:[~2023-04-17 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 8:04 wangmy [this message]
2023-04-17 8:04 ` [OE-core] [PATCH] libsolv: upgrade 0.7.23 -> 0.7.24 wangmy
2023-04-17 8:04 ` [OE-core] [PATCH] libxml2: upgrade 2.10.3 -> 2.10.4 wangmy
2023-04-17 8:04 ` [OE-core] [PATCH] boost: upgrade 1.81.0 -> 1.82.0 wangmy
2023-04-17 8:04 ` [OE-core] [PATCH] ofono: upgrade 2.0 -> 2.1 wangmy
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=1681718671-19418-1-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