From: Yash Shinde <yashinde145@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Umesh.Kallapa@windriver.com,
Naveen.Gowda@windriver.com, Sundeep.Kokkonda@windriver.com,
Shivaprasad.Moodalappa@windriver.com, Yash.Shinde@windriver.com
Subject: glibc: stable 2.37 branch updates.
Date: Fri, 17 Feb 2023 19:04:16 +0530 [thread overview]
Message-ID: <20230217133416.2352274-1-yashinde145@gmail.com> (raw)
Below commits on glibc-2.37 stable branch are updated.
d8e1a7590d elf: Smoke-test ldconfig -p against system /etc/ld.so.cache
6fe86ecd78 NEWS: Document CVE-2023-25139.
07b9521fc6 Account for grouping in printf width (bug 30068)
fb7b95dc47 Use 64-bit time_t interfaces in strftime and strptime (bug 30053)
9f8513dc64 LoongArch: Add new relocation types.
020b43544a cdefs: Limit definition of fortification macros
Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com>
---
meta/recipes-core/glibc/glibc-version.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/glibc/glibc-version.inc b/meta/recipes-core/glibc/glibc-version.inc
index bf6a8c9bd4..1b8665a9d8 100644
--- a/meta/recipes-core/glibc/glibc-version.inc
+++ b/meta/recipes-core/glibc/glibc-version.inc
@@ -1,6 +1,6 @@
SRCBRANCH ?= "release/2.37/master"
PV = "2.37"
-SRCREV_glibc ?= "a704fd9a133bfb10510e18702f48a6a9c88dbbd5"
+SRCREV_glibc ?= "d8e1a7590d375159fb5aac07ad8111ab4699e994"
SRCREV_localedef ?= "794da69788cbf9bf57b59a852f9f11307663fa87"
GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git"
--
2.34.1
next reply other threads:[~2023-02-17 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 13:34 Yash Shinde [this message]
2023-02-17 13:39 ` glibc: stable 2.37 branch updates Shinde, Yash
2023-02-17 13:46 ` Shinde, Yash
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=20230217133416.2352274-1-yashinde145@gmail.com \
--to=yashinde145@gmail.com \
--cc=Naveen.Gowda@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Shivaprasad.Moodalappa@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=Umesh.Kallapa@windriver.com \
--cc=Yash.Shinde@windriver.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 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.