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: minor wording fixes Date: Sun, 30 Jul 2023 17:46:20 +0000 (GMT) [thread overview] Message-ID: <20230730174620.B57683858D35@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=d5e321d1544ab467e86f3c3bc032951789663856 commit d5e321d1544ab467e86f3c3bc032951789663856 Author: Andreas K. Hüttel <dilfridge@gentoo.org> Date: Sun Jul 30 19:43:50 2023 +0200 NEWS: minor wording fixes Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> Diff: --- NEWS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 455ba9553b..d75c4b6688 100644 --- a/NEWS +++ b/NEWS @@ -56,7 +56,7 @@ Major new features: Deprecated and removed features, and other changes affecting compatibility: -* libcrypt is no longer built by default, one may use the "--enable-crypt" +* libcrypt is no longer built by default; one may use the "--enable-crypt" option to build libcrypt. libcrypt is likely to be removed from the GNU C Library in a future release, so it is recommended that applications port away from it to an alternative such as libxcrypt. @@ -77,7 +77,7 @@ Deprecated and removed features, and other changes affecting compatibility: Changes to build and runtime requirements: -* Building libmvec on AArch64 requires at minimum GCC 10 for SVE ACLE. +* Building libmvec on AArch64 requires at minimum GCC 10.1.0 for SVE ACLE. Security related changes:
reply other threads:[~2023-07-30 17:46 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=20230730174620.B57683858D35@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: linkBe 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).