From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dmitry Chestnykh <dm.chestnykh@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/3] package/uclibc: Bump to 1.0.48.
Date: Mon, 6 May 2024 22:39:13 +0200 [thread overview]
Message-ID: <20240506223913.31a83b67@windsurf> (raw)
In-Reply-To: <20240502045518.4875-1-dm.chestnykh@gmail.com>
On Thu, 2 May 2024 07:55:16 +0300
Dmitry Chestnykh <dm.chestnykh@gmail.com> wrote:
> - In 1.0.48 release uClibc-ng has provided the fix
> for SPARC related to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784
> - The hash for COPYING.LIB was changed because '^L' (0x0C) characters
> were removed from COPYING.LIB in uClibc-ng repo.
>
> Signed-off-by: Dmitry Chestnykh <dm.chestnykh@gmail.com>
> ---
> v1 -> v2:
> - Describe the change of COPYING.LIB hash.
> ---
> package/uclibc/uclibc.hash | 6 +++---
> package/uclibc/uclibc.mk | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
Applied to master, with minor commit log fixups. Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-06 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 4:55 [Buildroot] [PATCH v2 1/3] package/uclibc: Bump to 1.0.48 Dmitry Chestnykh
2024-05-02 4:55 ` [Buildroot] [PATCH v2 2/3] arch/Config.in: Allow building buildroot toolchain Dmitry Chestnykh
2024-05-06 20:39 ` Thomas Petazzoni via buildroot
2024-05-02 4:55 ` [Buildroot] [PATCH v2 3/3] configs/qemu_sparc_ss10_defconfig: Re-introduce Dmitry Chestnykh
2024-05-06 20:40 ` Thomas Petazzoni via buildroot
2024-05-06 20:39 ` Thomas Petazzoni via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-01 9:37 [Buildroot] [PATCH v2 1/3] package/uclibc: Bump to 1.0.48 Dmitry Chestnykh
2024-05-01 12:10 ` Waldemar Brodkorb
2024-05-01 18:20 ` Yann E. MORIN
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=20240506223913.31a83b67@windsurf \
--to=buildroot@buildroot.org \
--cc=dm.chestnykh@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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