From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed] Fix typo in error messages
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20190313131421.GA4179@delia> (raw)
Hi,
Fix typos in error message:
- "enconding" -> "encoding"
- "differentpointer" -> "different pointer"
Committed to trunk.
Thanks,
- Tom
Fix typo in error messages
2019-03-13 Tom de Vries <tdevries@suse.de>
* dwz.c (read_dwarf, write_multifile): Fix typo in error messages.
---
dwz.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dwz.c b/dwz.c
index 476807a..6b6a33e 100644
--- a/dwz.c
+++ b/dwz.c
@@ -9946,7 +9946,7 @@ read_dwarf (DSO *dso, bool quieter)
init_endian (dso->ehdr.e_ident[EI_DATA]);
else
{
- error (0, 0, "%s: Wrong ELF data enconding", dso->filename);
+ error (0, 0, "%s: Wrong ELF data encoding", dso->filename);
return 1;
}
@@ -10790,7 +10790,7 @@ write_multifile (DSO *dso)
? ELFDATA2LSB : ELFDATA2MSB)))
{
error (0, 0, "Multi-file optimization not allowed for different"
- "pointer sizes or endianity");
+ " pointer sizes or endianity");
multifile = NULL;
return 1;
}
reply other threads:[~2019-03-13 13:13 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=20190313131421.GA4179@delia \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).