mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Elijah Newren via GitGitGadget" <>
Cc: Elijah Newren <>, Elijah Newren <>
Subject: [PATCH 2/2] hashmap: fix typo in usage docs
Date: Tue, 28 Jul 2020 20:45:39 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

From: Elijah Newren <>

Signed-off-by: Elijah Newren <>
 hashmap.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hashmap.h b/hashmap.h
index 79ae9f80de..ef220de4c6 100644
--- a/hashmap.h
+++ b/hashmap.h
@@ -168,7 +168,7 @@ struct hashmap_entry {
  * argument `keydata`, respectively. Otherwise, `keydata` is NULL.
  * When it is too expensive to allocate a user entry (either because it is
- * large or varialbe sized, such that it is not on the stack), then the
+ * large or variable sized, such that it is not on the stack), then the
  * relevant data to check for equality should be passed via `keydata`.
  * In this case `key` can be a stripped down version of the user key data
  * or even just a hashmap_entry having the correct hash.

  parent reply	other threads:[~2020-07-28 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 20:45 [PATCH 0/2] Typo fixes Elijah Newren via GitGitGadget
2020-07-28 20:45 ` [PATCH 1/2] Remove doubled words in various comments Elijah Newren via GitGitGadget
2020-07-28 20:45 ` Elijah Newren via GitGitGadget [this message]
2020-07-28 20:48 ` [PATCH 0/2] Typo fixes Taylor Blau
2020-07-28 21:27   ` 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:

  List information:

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

  git send-email \ \ \ \ \

* 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

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).