From: "Martin Liška" <mliska@suse.cz>
To: binutils@sourceware.org
Subject: [PATCH] ld: fix NEWS typos
Date: Mon, 8 Aug 2022 13:23:18 +0200 [thread overview]
Message-ID: <a39452e1-ff31-2447-36a4-c5c7035af4cb@suse.cz> (raw)
I'm going to push this as obvious (same to 2.39 branch).
Cheers,
Martin
ld/ChangeLog:
* NEWS: Fix 2 typos.
---
ld/NEWS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ld/NEWS b/ld/NEWS
index 40f7059b897..355752e6b24 100644
--- a/ld/NEWS
+++ b/ld/NEWS
@@ -27,10 +27,10 @@ Changes in 2.39:
--enable-warn-rwx-segments=no
will make --no-warn-rwx-segments enabled by default.
- --enable-defaul-execstack=no
+ --enable-default-execstack=no
will stop the creation of an executable stack simply because an input file
is missing a .note.GNU-stack section, even on architectures where this
- ehaviour is the default.
+ behaviour is the default.
* TYPE=<type> is now supported in an output section description to set the
section type value.
--
2.37.1
next reply other threads:[~2022-08-08 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 11:23 Martin Liška [this message]
2022-08-08 11:26 ` Martin Liška
2022-08-08 14:44 ` Nick Clifton
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=a39452e1-ff31-2447-36a4-c5c7035af4cb@suse.cz \
--to=mliska@suse.cz \
--cc=binutils@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).