threads / patch / 61292

patchtypo: Replace 'commitish' with 'committish'

Subject: [PATCH] typo: Replace 'commitish' with 'committish'

## tl;dr

2 messages between Apr 7, 2024 and Apr 10, 2024. Diffs are folded; open one to read it.

replies: 1people: 2as markdown or json

Pi Fisher· Apr 7, 2024, 21:21 UTC · lore

Across only three files, comments and a single function name used 'commitish' rather than 'commit-ish' or 'committish' as the spelling. The git glossary accepts a hyphen or a double-t, but not a single-t. Despite the typo in a translation file, none of the typos appear in user-visible locations.

Signed-off-by: Pi Fisher <Pi.L.D.Fisher@gmail.com>
---
The function name was renamed to use 'committish', preferring to avoid a
hyphenated word. Comments referencing this function were rewritten to
match the new name. In the translation file, 'commit-ish' appeared
multiple times, but 'committish' appeared only once, so I changed the
comment to match the more popular option.
 branch.c | 10 +++++-----
 branch.h | 14 +++++++-------
 po/tr.po |  2 +-
 3 files changed, 13 insertions(+), 13 deletions(-)
Show changes to 3 files +13 −13

branch.c, branch.h, po/tr.po

diff --git a/branch.c b/branch.c
index 6719a181bd..b8f8fd4979 100644
--- a/branch.c
+++ b/branch.c
@@ -734,7 +734,7 @@ static int submodule_create_branch(struct repository *r,
 }
 
 void create_branches_recursively(struct repository *r, const char *name,
-				 const char *start_commitish,
+				 const char *start_committish,
 				 const char *tracking_name, int force,
 				 int reflog, int quiet, enum branch_track track,
 				 int dry_run)
@@ -744,8 +744,8 @@ void create_branches_recursively(struct repository *r, const char *name,
 	struct object_id super_oid;
 	struct submodule_entry_list submodule_entry_list;
 
-	/* Perform dwim on start_commitish to get super_oid and branch_point. */
-	dwim_branch_start(r, start_commitish, BRANCH_TRACK_NEVER,
+	/* Perform dwim on start_committish to get super_oid and branch_point. */
+	dwim_branch_start(r, start_committish, BRANCH_TRACK_NEVER,
 			  &branch_point, &super_oid);
 
 	/*
@@ -768,7 +768,7 @@ void create_branches_recursively(struct repository *r, const char *name,
 				submodule_entry_list.entries[i].submodule->name);
 			if (advice_enabled(ADVICE_SUBMODULES_NOT_UPDATED))
 				advise(_("You may try updating the submodules using 'git checkout --no-recurse-submodules %s && git submodule update --init'"),
-				       start_commitish);
+				       start_committish);
 			exit(code);
 		}
 
@@ -783,7 +783,7 @@ void create_branches_recursively(struct repository *r, const char *name,
 			    name);
 	}
 
-	create_branch(r, name, start_commitish, force, 0, reflog, quiet,
+	create_branch(r, name, start_committish, force, 0, reflog, quiet,
 		      BRANCH_TRACK_NEVER, dry_run);
 	if (dry_run)
 		return;
diff --git a/branch.h b/branch.h
index 30c01aed73..ec2f35fda4 100644
--- a/branch.h
+++ b/branch.h
@@ -78,26 +78,26 @@ void create_branch(struct repository *r,
  * those of create_branch() except for start_name, which is represented
  * by two different parameters:
  *
- * - start_commitish is the commit-ish, in repository r, that determines
+ * - start_committish is the commit-ish, in repository r, that determines
  *   which commits the branches will point to. The superproject branch
- *   will point to the commit of start_commitish and the submodule
- *   branches will point to the gitlink commit oids in start_commitish's
+ *   will point to the commit of start_committish and the submodule
+ *   branches will point to the gitlink commit oids in start_committish's
  *   tree.
  *
  * - tracking_name is the name of the ref, in repository r, that will be
  *   used to set up tracking information. This value is propagated to
  *   all submodules, which will evaluate the ref using their own ref
- *   stores. If NULL, this defaults to start_commitish.
+ *   stores. If NULL, this defaults to start_committish.
  *
- * When this function is called on the superproject, start_commitish
+ * When this function is called on the superproject, start_committish
  * can be any user-provided ref and tracking_name can be NULL (similar
  * to create_branches()). But when recursing through submodules,
- * start_commitish is the plain gitlink commit oid. Since the oid cannot
+ * start_committish is the plain gitlink commit oid. Since the oid cannot
  * be used for tracking information, tracking_name is propagated and
  * used for tracking instead.
  */
 void create_branches_recursively(struct repository *r, const char *name,
-				 const char *start_commitish,
+				 const char *start_committish,
 				 const char *tracking_name, int force,
 				 int reflog, int quiet, enum branch_track track,
 				 int dry_run);
diff --git a/po/tr.po b/po/tr.po
index 19d6661bbe..5837752d0b 100644
--- a/po/tr.po
+++ b/po/tr.po
@@ -20,7 +20,7 @@
 # clone                       | klon(lamak)                 #
 # commit (ad)                 | işleme                      #
 # commit (eyl.)               | işlemek                     #
-# commitish                   | işlememsi                   #
+# commit-ish                  | işlememsi                   #
 # conflict                    | çakışma                     #
 # cruft                       | süprüntü                    #
 # dangling object             | sallanan nesne              #

base-commit: 3c2a3fdc388747b9eaf4a4a4f2035c1c9ddb26d0
-- 
2.34.1
Junio C Hamano· Apr 10, 2024, 21:15 UTC · re: Pi Fisher · lore

Re: [PATCH] typo: Replace 'commitish' with 'committish'

Pi Fisher <pi.l.d.fisher@gmail.com> writes:
Show 13 quoted lines
> Across only three files, comments and a single function name used
> 'commitish' rather than 'commit-ish' or 'committish' as the spelling.
> The git glossary accepts a hyphen or a double-t, but not a single-t.
> Despite the typo in a translation file, none of the typos appear in
> user-visible locations.
>
> Signed-off-by: Pi Fisher <Pi.L.D.Fisher@gmail.com>
> ---
> The function name was renamed to use 'committish', preferring to avoid a
> hyphenated word. Comments referencing this function were rewritten to
> match the new name. In the translation file, 'commit-ish' appeared
> multiple times, but 'committish' appeared only once, so I changed the
> comment to match the more popular option.
Sounds good.  Thanks.

← back to recent threads