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

Re: Defining timestamp_t as intmax_t instead of uintmax_t

From
Arnav Bhate <bhatearnav@gmail.com>
Date
Mar 11, 2025, 10:54 UTC
Message-ID
<65ea4bed-1513-4721-af63-1ebc78194a7d@gmail.com>
In-Reply-To
<629c3c21-ab11-42c1-8cb1-34698e736db6@gmail.com>
Arnav Bhate <bhatearnav@gmail.com> writes:
> This also means git cannot deal with time before 1970, though I can't
> think of a scenario where it will have to.

I just tested and found that if the user enters dates before 1970 the output is incorrect, for example with git log. This error also seems to propagate to GitHub. This may or may not be related to using uintmax_t, however it seems likely.

-- 
Regards,
Arnav Bhate
(He/Him)
Previous: Arnav BhateNext: Junio C Hamano
Message 2 of 4 in “Defining timestamp_t as intmax_t instead of uintmax_t”
  1. Arnav BhateMar 11, 2025
  2. Arnav BhateMar 11, 2025
  3. Junio C HamanoMar 11, 2025
  4. Arnav BhateMar 11, 2025

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.