From: Andrei Rybak <rybak.a.v@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH v1 3/3] difftool: add space after full stop in comments
Date: Sat, 2 Oct 2021 20:44:07 +0200 [thread overview]
Message-ID: <20211002184407.117282-4-rybak.a.v@gmail.com> (raw)
In-Reply-To: <20211002184407.117282-1-rybak.a.v@gmail.com>
These punctuation typos were found using:
git grep -P ' [a-z0-9A-Z-]+[.][A-Z][A-Za-z-]+ '
Signed-off-by: Andrei Rybak <rybak.a.v@gmail.com>
---
I've also looked for similar typos around commas and semicolons and didn't find
any.
builtin/difftool.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/builtin/difftool.c b/builtin/difftool.c
index bb9fe7245a..d9a4e55caf 100644
--- a/builtin/difftool.c
+++ b/builtin/difftool.c
@@ -529,7 +529,7 @@ static int run_dir_diff(const char *extcmd, int symlinks, const char *prefix,
goto finish;
/*
- * Changes to submodules require special treatment.This loop writes a
+ * Changes to submodules require special treatment. This loop writes a
* temporary file to both the left and right directories to show the
* change in the recorded SHA1 for the submodule.
*/
@@ -548,7 +548,7 @@ static int run_dir_diff(const char *extcmd, int symlinks, const char *prefix,
}
/*
- * Symbolic links require special treatment.The standard "git diff"
+ * Symbolic links require special treatment. The standard "git diff"
* shows only the link itself, not the contents of the link target.
* This loop replicates that behavior.
*/
--
2.33.0
next prev parent reply other threads:[~2021-10-02 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 18:44 [PATCH v1 0/3] Typofixes Andrei Rybak
2021-10-02 18:44 ` [PATCH v1 1/3] *: spell Latin abbreviations correctly Andrei Rybak
2021-10-02 19:40 ` Elijah Newren
2021-10-02 20:08 ` Ævar Arnfjörð Bjarmason
2021-10-02 18:44 ` [PATCH v1 2/3] *: fix spelling typos Andrei Rybak
2021-10-02 19:34 ` Elijah Newren
2021-10-02 18:44 ` Andrei Rybak [this message]
2021-10-02 19:36 ` [PATCH v1 3/3] difftool: add space after full stop in comments Elijah Newren
2021-10-02 20:12 ` Carlo Arenas
2021-10-02 23:41 ` Elijah Newren
2021-10-11 15:42 ` David Aguilar
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=20211002184407.117282-4-rybak.a.v@gmail.com \
--to=rybak.a.v@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).