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.