From: Stefan Liebler <stli@linux.ibm.com>
To: Sam James <sam@gentoo.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] S390: Fix building with --disable-mutli-arch [BZ #31196]
Date: Wed, 31 Jan 2024 13:03:48 +0100 [thread overview]
Message-ID: <d5114564-97dd-4caf-b5ed-7db13a4ae4ad@linux.ibm.com> (raw)
In-Reply-To: <874jeu8x58.fsf@gentoo.org>
On 30.01.24 19:59, Sam James wrote:
>
> Stefan Liebler <stli@linux.ibm.com> writes:
>
>> Starting with commits
>> - 7ea510127e2067efa07865158ac92c330c379950
>> string: Add libc_hidden_proto for strchrnul
>> - 22999b2f0fb62eed1af4095d062bd1272d6afeb1
>> string: Add libc_hidden_proto for memrchr
>
> Nit: s/mutli/multi/ in title (it's obvious what it means ofc but
> mentioning it because it impacts ability to grep).
>
> Thanks!
Sorry. Too late. Andreas has already committed it to be within glibc
2.39 release.
prev parent reply other threads:[~2024-01-31 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 8:34 Stefan Liebler
2024-01-30 17:21 ` Adhemerval Zanella Netto
2024-01-31 12:06 ` Stefan Liebler
2024-01-30 18:59 ` Sam James
2024-01-31 12:03 ` Stefan Liebler [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=d5114564-97dd-4caf-b5ed-7db13a4ae4ad@linux.ibm.com \
--to=stli@linux.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=sam@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).