public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andreas K. Huttel <dilfridge@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] NEWS: Fix typos
Date: Mon, 31 Jul 2023 17:54:42 +0000 (GMT) [thread overview]
Message-ID: <20230731175442.0EBB73858CD1@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=36f2487f13e3540be9ee0fb51876b1da72176d3f
commit 36f2487f13e3540be9ee0fb51876b1da72176d3f
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date: Mon Jul 31 19:54:16 2023 +0200
NEWS: Fix typos
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
Diff:
---
NEWS | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/NEWS b/NEWS
index d75c4b6688..872bc8907b 100644
--- a/NEWS
+++ b/NEWS
@@ -69,7 +69,7 @@ Deprecated and removed features, and other changes affecting compatibility:
5.4.228, 4.19.270 or 4.14.303.
* The "--disable-experimental-malloc" option is no longer available. The
- per-thread cache can still be disable per-application using tunables
+ per-thread cache can still be disabled per-application using tunables
(glibc.malloc.tcache_count set to zero).
* The configure option "--enable-tunables" has been removed. The tunable
@@ -77,7 +77,8 @@ Deprecated and removed features, and other changes affecting compatibility:
Changes to build and runtime requirements:
-* Building libmvec on AArch64 requires at minimum GCC 10.1.0 for SVE ACLE.
+* Building libmvec on AArch64 requires at a minimum GCC 10.1.0 for SVE
+ ACLE.
Security related changes:
reply other threads:[~2023-07-31 17:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230731175442.0EBB73858CD1@sourceware.org \
--to=dilfridge@sourceware.org \
--cc=glibc-cvs@sourceware.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).