From: Li Peng <lip@dtdream.com>
To: git@vger.kernel.org
Cc: tboegi@web.de, Li Peng <lip@dtdream.com>
Subject: [PATCH] precompose-utf8: fix typo of "sequences"
Date: Fri, 6 May 2016 19:55:10 +0800 [thread overview]
Message-ID: <1462535710-16382-1-git-send-email-lip@dtdream.com> (raw)
Fix a typo in comment.
Signed-off-by: Li Peng <lip@dtdream.com>
---
compat/precompose_utf8.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/compat/precompose_utf8.c b/compat/precompose_utf8.c
index dfbe6d8..4293b53 100644
--- a/compat/precompose_utf8.c
+++ b/compat/precompose_utf8.c
@@ -147,7 +147,7 @@ struct dirent_prec_psx *precompose_utf8_readdir(PREC_DIR *prec_dir)
if (errno || inleft) {
/*
* iconv() failed and errno could be E2BIG, EILSEQ, EINVAL, EBADF
- * MacOS X avoids illegal byte sequemces.
+ * MacOS X avoids illegal byte sequences.
* If they occur on a mounted drive (e.g. NFS) it is not worth to
* die() for that, but rather let the user see the original name
*/
--
1.8.3.1
next reply other threads:[~2016-05-06 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 11:55 Li Peng [this message]
2016-05-06 12:24 ` [PATCH] precompose-utf8: fix typo of "sequences" Torsten Bögershausen
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=1462535710-16382-1-git-send-email-lip@dtdream.com \
--to=lip@dtdream.com \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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 NNTP newsgroup(s).