From: Li Peng <lip@dtdream.com>
To: git@vger.kernel.org
Cc: peff@peff.net, Li Peng <lip@dtdream.com>
Subject: [PATCH] utf8: fix duplicate words of "the"
Date: Fri, 6 May 2016 20:31:33 +0800 [thread overview]
Message-ID: <1462537893-18493-1-git-send-email-lip@dtdream.com> (raw)
Fix duplicate words of "the" in comment.
Signed-off-by: Li Peng <lip@dtdream.com>
---
transport-helper.c | 2 +-
utf8.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/transport-helper.c b/transport-helper.c
index b934183..13b7a57 100644
--- a/transport-helper.c
+++ b/transport-helper.c
@@ -1152,7 +1152,7 @@ static void udt_close_if_finished(struct unidirectional_transfer *t)
}
/*
- * Tries to read read data from source into buffer. If buffer is full,
+ * Tries to read data from source into buffer. If buffer is full,
* no data is read. Returns 0 on success, -1 on error.
*/
static int udt_do_read(struct unidirectional_transfer *t)
diff --git a/utf8.h b/utf8.h
index 7930b44..6bbcf31 100644
--- a/utf8.h
+++ b/utf8.h
@@ -48,7 +48,7 @@ static inline char *reencode_string(const char *in,
int mbs_chrlen(const char **text, size_t *remainder_p, const char *encoding);
/*
- * Returns true if the the path would match ".git" after HFS case-folding.
+ * Returns true if the path would match ".git" after HFS case-folding.
* The path should be NUL-terminated, but we will match variants of both ".git\0"
* and ".git/..." (but _not_ ".../.git"). This makes it suitable for both fsck
* and verify_path().
--
1.8.3.1
next reply other threads:[~2016-05-06 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 12:31 Li Peng [this message]
2016-05-06 13:09 ` [PATCH] utf8: fix duplicate words of "the" Jeff King
2016-05-06 17:28 ` Junio C Hamano
2016-05-06 18:30 ` Junio C Hamano
2016-05-07 15:10 ` 回复:[PATCH] " 李三0159
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=1462537893-18493-1-git-send-email-lip@dtdream.com \
--to=lip@dtdream.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).