Jeff King <peff@xxxxxxxx> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html