git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew Kreimer via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Andrew Kreimer <algonell@gmail.com>, Andrew Kreimer <algonell@gmail.com>
Subject: [PATCH 02/20] diffcore-rename: fix typos
Date: Thu, 19 Sep 2024 18:34:22 +0000	[thread overview]
Message-ID: <f469df28c89974185377661a01d927390a11b23f.1726770880.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1794.git.1726770880.gitgitgadget@gmail.com>

From: Andrew Kreimer <algonell@gmail.com>

Fix typos in comments.

Signed-off-by: Andrew Kreimer <algonell@gmail.com>
---
 diffcore-rename.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/diffcore-rename.c b/diffcore-rename.c
index fab45b10d7e..3d6826baa3a 100644
--- a/diffcore-rename.c
+++ b/diffcore-rename.c
@@ -933,7 +933,7 @@ static int find_basename_matches(struct diff_options *options,
 	 * spend more cycles to find similarities between files, so it may
 	 * be less likely that this heuristic is wanted.  If someone is
 	 * doing break detection, that means they do not want filename
-	 * similarity to imply any form of content similiarity, and thus
+	 * similarity to imply any form of content similarity, and thus
 	 * this heuristic would definitely be incompatible.
 	 */
 
@@ -1534,7 +1534,7 @@ void diffcore_rename_extended(struct diff_options *options,
 		 *   - remove ones not found in relevant_sources
 		 * and
 		 *   - remove ones in relevant_sources which are needed only
-		 *     for directory renames IF no ancestory directory
+		 *     for directory renames IF no ancestry directory
 		 *     actually needs to know any more individual path
 		 *     renames under them
 		 */
-- 
gitgitgadget


  parent reply	other threads:[~2024-09-19 18:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 18:34 [PATCH 00/20] Fix typos Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 01/20] config.mak.dev: fix a typo Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` Andrew Kreimer via GitGitGadget [this message]
2024-09-19 18:34 ` [PATCH 03/20] fsmonitor-settings: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 04/20] git-instaweb: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 05/20] git-p4: fix typos Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 06/20] gpg-interface: fix a typo Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 07/20] http: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 08/20] merge-ll: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 09/20] merge-ort: fix typos Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 10/20] object-file: fix a typo Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 11/20] pretty: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 12/20] read-cache-ll: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 13/20] rebase: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 14/20] ref-filter: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 15/20] refs: fix typos Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 16/20] revision: fix a typo Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 17/20] run-command: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 18/20] setup: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 19/20] sideband: " Andrew Kreimer via GitGitGadget
2024-09-19 18:34 ` [PATCH 20/20] upload-pack: " Andrew Kreimer via GitGitGadget
2024-09-19 19:35 ` [PATCH 00/20] Fix typos Eric Sunshine
2024-09-20  7:00   ` Andrew Kreimer
2024-09-19 20:33 ` Kristoffer Haugsbakk
2024-09-19 20:42   ` Junio C Hamano
2024-09-19 20:54     ` Eric Sunshine
2024-09-19 20:57       ` Junio C Hamano

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=f469df28c89974185377661a01d927390a11b23f.1726770880.git.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=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).