git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2 1/6] doc: patch-id: don’t use semicolon between bullet points

From
Kkristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
Date
Jan 9, 2026, 14:25 UTC
Message-ID
<V2_no_semicolon.1b3@msgid.xyz>
In-Reply-To
<V2_CV_doc_patch-id_3.1b2@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>

These bullet points are full-fledged paragraphs with sentences. It’s best to restrict semicolon-termination to the case when the bullet list amounts to a list of items.[1]

† 1: Like “List: ... • first; ... • second; and ... • third.”
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
 Documentation/git-patch-id.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-patch-id.adoc b/Documentation/git-patch-id.adoc
index 92a1af36a27..bac37db09d4 100644
--- a/Documentation/git-patch-id.adoc
+++ b/Documentation/git-patch-id.adoc
@@ -45,7 +45,7 @@ This is the default if `patchid.verbatim` is `true`.
   with two different settings for `-O<orderfile>` result in the same
   patch ID signature, thereby allowing the computed result to be used
   as a key to index some meta-information about the change between
-  the two trees;
+  the two trees.
 
 - Result is different from the value produced by git 1.9 and older
   or produced when an "unstable" hash (see `--unstable` below) is
-- 
2.52.0.421.gc32ead4fc78
Previous: kristofferhaugsbakk@fastmail.comNext: kristofferhaugsbakk@fastmail.com
Message 14 of 20 in “doc: patch-id: six small improvements”
  1. 0/6 doc: patch-id: six small improvementskristofferhaugsbakk@fastmail.com, Jan 8, 2026
  2. 1/6 doc: patch-id: don’t use semicolon between bullet pointskristofferhaugsbakk@fastmail.com, Jan 8, 2026
  3. 2/6 doc: patch-id: capitalize Git versionkristofferhaugsbakk@fastmail.com, Jan 8, 2026
  4. 3/6 patch-id: use “patch ID” throughoutkristofferhaugsbakk@fastmail.com, Jan 8, 2026
  5. 4/6 doc: patch-id: use definite article for the resultkristofferhaugsbakk@fastmail.com, Jan 8, 2026
  6. 5/6 doc: patch-id: spell out the git-diff-tree(1) formkristofferhaugsbakk@fastmail.com, Jan 8, 2026
  7. 6/6 doc: patch-id: --verbatim locks in --stablekristofferhaugsbakk@fastmail.com, Jan 8, 2026
  8. Pushkar SinghJan 8, 2026
  9. Kristoffer HaugsbakkJan 8, 2026
  10. Kristoffer HaugsbakkJan 8, 2026
  11. Patrick SteinhardtJan 9, 2026
  12. Kristoffer HaugsbakkJan 9, 2026
  13. 0/6 doc: patch-id: six small improvementskristofferhaugsbakk@fastmail.com, Jan 9, 2026
  14. 1/6 doc: patch-id: don’t use semicolon between bullet pointskristofferhaugsbakk@fastmail.com, Jan 9, 2026
  15. 2/6 doc: patch-id: capitalize Git versionkristofferhaugsbakk@fastmail.com, Jan 9, 2026
  16. 3/6 patch-id: use “patch ID” throughoutkristofferhaugsbakk@fastmail.com, Jan 9, 2026
  17. 4/6 doc: patch-id: use definite article for the resultkristofferhaugsbakk@fastmail.com, Jan 9, 2026
  18. 5/6 doc: patch-id: spell out the git-diff-tree(1) formkristofferhaugsbakk@fastmail.com, Jan 9, 2026
  19. 6/6 doc: patch-id: --verbatim locks in --stablekristofferhaugsbakk@fastmail.com, Jan 9, 2026
  20. Patrick SteinhardtJan 9, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.