git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Elijah Newren <newren@gmail.com>
Subject: [PATCH 3/3] name-hash.c: remove duplicate word in comment
Date: Tue, 05 Nov 2019 23:31:32 +0000	[thread overview]
Message-ID: <f7503d644c2baa9f5b8a71c998741f8232385508.1572996692.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.454.git.1572996692.gitgitgadget@gmail.com>

From: Elijah Newren <newren@gmail.com>

Signed-off-by: Elijah Newren <newren@gmail.com>
---
 name-hash.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/name-hash.c b/name-hash.c
index ceb1d7bd6f..4885bae5da 100644
--- a/name-hash.c
+++ b/name-hash.c
@@ -218,7 +218,7 @@ static int lookup_lazy_params(struct index_state *istate)
  * However, the hashmap is going to put items into bucket
  * chains based on their hash values.  Use that to create n
  * mutexes and lock on mutex[bucket(hash) % n].  This will
- * decrease the collision rate by (hopefully) by a factor of n.
+ * decrease the collision rate by (hopefully) a factor of n.
  */
 static void init_dir_mutex(void)
 {
-- 
gitgitgadget

  parent reply	other threads:[~2019-11-05 23:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 23:31 [PATCH 0/3] Other doc fixes Elijah Newren via GitGitGadget
2019-11-05 23:31 ` [PATCH 1/3] git-filter-branch.txt: correct argument name typo Elijah Newren via GitGitGadget
2019-11-05 23:31 ` [PATCH 2/3] hashmap: fix documentation misuses of -> versus Elijah Newren via GitGitGadget
2019-11-05 23:31 ` Elijah Newren via GitGitGadget [this message]
2019-11-07  5:41   ` [PATCH 3/3] name-hash.c: remove duplicate word in comment Junio C Hamano
2019-11-06  4:06 ` [PATCH 0/3] Other doc fixes Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7503d644c2baa9f5b8a71c998741f8232385508.1572996692.git.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newren@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).