git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Kreimer <algonell@gmail.com>
To: git@vger.kernel.org
Cc: Andrew Kreimer <algonell@gmail.com>
Subject: [PATCH 1/7] compat: fix typos
Date: Wed,  9 Oct 2024 14:49:34 +0300	[thread overview]
Message-ID: <20241009114940.520486-2-algonell@gmail.com> (raw)
In-Reply-To: <20241009114940.520486-1-algonell@gmail.com>

Fix typos via codespell.

Signed-off-by: Andrew Kreimer <algonell@gmail.com>
---
 compat/fsmonitor/fsm-listen-win32.c | 4 ++--
 compat/regex/regexec.c              | 2 +-
 compat/simple-ipc/ipc-unix-socket.c | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/compat/fsmonitor/fsm-listen-win32.c b/compat/fsmonitor/fsm-listen-win32.c
index 80e092b511..9a6efc9bea 100644
--- a/compat/fsmonitor/fsm-listen-win32.c
+++ b/compat/fsmonitor/fsm-listen-win32.c
@@ -431,9 +431,9 @@ static int recv_rdcw_watch(struct one_watch *watch)
 	 * but I observed ERROR_ACCESS_DENIED (0x05) errors during
 	 * testing.
 	 *
-	 * Note that we only get notificaiton events for events
+	 * Note that we only get notification events for events
 	 * *within* the directory, not *on* the directory itself.
-	 * (These might be properies of the parent directory, for
+	 * (These might be properties of the parent directory, for
 	 * example).
 	 *
 	 * NEEDSWORK: We might try to check for the deleted directory
diff --git a/compat/regex/regexec.c b/compat/regex/regexec.c
index e92be5741d..15ab2d1d40 100644
--- a/compat/regex/regexec.c
+++ b/compat/regex/regexec.c
@@ -292,7 +292,7 @@ compat_symbol (libc, __compat_regexec, regexec, GLIBC_2_0);
    concerned.
 
    If REGS is not NULL, and BUFP->no_sub is not set, the offsets of the match
-   and all groups is stroed in REGS.  (For the "_2" variants, the offsets are
+   and all groups is stored in REGS.  (For the "_2" variants, the offsets are
    computed relative to the concatenation, not relative to the individual
    strings.)
 
diff --git a/compat/simple-ipc/ipc-unix-socket.c b/compat/simple-ipc/ipc-unix-socket.c
index 57d919c6b4..7db3b2a897 100644
--- a/compat/simple-ipc/ipc-unix-socket.c
+++ b/compat/simple-ipc/ipc-unix-socket.c
@@ -713,7 +713,7 @@ static int accept_thread__wait_for_connection(
  * Block SIGPIPE in this thread for the life of the thread.  This
  * avoids any stray SIGPIPE signals when closing pipe fds under
  * extremely heavy loads (such as when the fifo queue is full and we
- * drop incomming connections).
+ * drop incoming connections).
  */
 static void *accept_thread_proc(void *_accept_thread_data)
 {
-- 
2.39.5


  reply	other threads:[~2024-10-09 11:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 11:49 [PATCH 0/7] Fix typos Andrew Kreimer
2024-10-09 11:49 ` Andrew Kreimer [this message]
2024-10-10  6:55   ` [PATCH 1/7] compat: fix typos Patrick Steinhardt
2024-10-10 15:14     ` Andrew Kreimer
2024-10-09 11:49 ` [PATCH 2/7] contrib: " Andrew Kreimer
2024-10-09 11:49 ` [PATCH 3/7] git-gui: Fix typos Andrew Kreimer
2024-10-09 11:49 ` [PATCH 4/7] t: fix typos Andrew Kreimer
2024-10-09 11:49 ` [PATCH 5/7] t/perf: " Andrew Kreimer
2024-10-09 11:49 ` [PATCH 6/7] t/unit-tests: " Andrew Kreimer
2024-10-09 11:49 ` [PATCH 7/7] t/helper: fix a typo Andrew Kreimer

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=20241009114940.520486-2-algonell@gmail.com \
    --to=algonell@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).