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

[PATCH] doc: fix a small, old release notes typo

From
D. Ben Knoble <ben.knoble+github@gmail.com>
Date
Jun 14, 2026, 17:28 UTC
Message-ID
<645638cd87d6d919af6d4310be8176d49fba326e.1781456960.git.ben.knoble+github@gmail.com>
Signed-off-by: D. Ben Knoble <ben.knoble+github@gmail.com>
---
No harm done if you choose not to keep this, I think. Stumbled upon it when
trying to understand Elijah's message [1] about timestamp_t overflowing in 2106
(I though 32-bit time_t overflowed in 2038, but timestamp_t is something
different… except maybe when it's not? Anyway…)
[1]: <pull.2148.git.1781420271100.gitgitgadget@gmail.com>
 Documentation/RelNotes/2.14.0.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/RelNotes/2.14.0.adoc b/Documentation/RelNotes/2.14.0.adoc
index 2711a2529d..182fbe6179 100644
--- a/Documentation/RelNotes/2.14.0.adoc
+++ b/Documentation/RelNotes/2.14.0.adoc
@@ -142,7 +142,7 @@ Performance, Internal Implementation, Development Support etc.
    historical use of ulong for timestamp would mean they cannot
    represent some timestamp that the platform allows.  Invent a
    separate and dedicated timestamp_t (so that we can distinguish
-   timestamps and a vanilla ulongs, which along is already a good
+   timestamps and a vanilla ulongs, which alone is already a good
    move), and then declare uintmax_t is the type to be used as the
    timestamp_t.
 

base-commit: 0c8ab3ebcc76981376809c8fe632d0fe18e93347
-- 
2.54.0.1136.gdb2ca164c4.dirty
Next: Junio C Hamano
Message 1 of 5 in “doc: fix a small, old release notes typo”
  1. doc: fix a small, old release notes typoD. Ben Knoble, Jun 14, 2026
  2. Junio C HamanoJun 14, 2026
  3. D. Ben KnobleJun 15, 2026
  4. Jeff KingJun 15, 2026
  5. D. Ben KnobleJun 15, 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.