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

Re: [PATCH 0/3] fix local_tzoffset with far-in-future dates

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 20, 2016, 22:11 UTC
Message-ID
<xmqqy45zse7o.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160620210901.GE3631@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> I still don't know how that screwed-up timestamp got _into_
> a commit, so perhaps there is another bug lurking.  I couldn't convince
> git to parse anything beyond 2100, and committing with
> GIT_AUTHOR_DATE='@5758122296 +0000' works just fine.
Interesting.  The weirdest I could come up with was with
    GIT_AUTHOR_DATE='@5758122296 -9999

which gets turned into the same timestamp but with -10039 timezone (simply because 99 minutes is an hour and 39 minutes).

>   [1/3]: t0006: rename test-date's "show" to "relative"
>   [2/3]: t0006: test various date formats
>   [3/3]: local_tzoffset: detect errors from tm_to_time_t
Thanks, will queue.
Previous: Jeff KingNext: Jeff King
Message 5 of 8 in “fix local_tzoffset with far-in-future dates”
  1. 0/3 fix local_tzoffset with far-in-future datesJeff King, Jun 20, 2016
  2. 2/3 t0006: test various date formatsJeff King, Jun 20, 2016
  3. 3/3 local_tzoffset: detect errors from tm_to_time_tJeff King, Jun 20, 2016
  4. 1/3 t0006: rename test-date's "show" to "relative"Jeff King, Jun 20, 2016
  5. Junio C HamanoJun 20, 2016
  6. Jeff KingJun 20, 2016
  7. Norbert KieselJun 21, 2016
  8. Jeff KingJun 21, 2016

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.