From: D. Ben Knoble Date: Sun, 14 Jun 2026 17:28:31 GMT Subject: [PATCH] doc: fix a small, old release notes typo Message-ID: <645638cd87d6d919af6d4310be8176d49fba326e.1781456960.git.ben.knoble+github@gmail.com> Signed-off-by: D. Ben Knoble --- 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]: 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