[issue2513] Unix Mercurial can record timestamps Windows Mercurial cannot read

[Benjamin Pollack]

New submission from Benjamin Pollack <benjamin at bitquabit.com>:

Due to clock skew on a server, a Mercurial changeset got committed with
timestamp -802511389.0. For whatever reason, the Unix version of Python's
time.gmtime can successfully convert this to a valid if weird value
(specifically July 27, 1944), where the Windows version of time.gmtime
simply crashes with a value error.

It seems Mercurial should both prevent bogus date values from being
recorded, and should prevent bad values from crashing Mercurial.

----------
messages: 14485
nosy: benjamin
priority: bug
status: unread
title: Unix Mercurial can record timestamps Windows Mercurial cannot read
topic: windows

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2513>
____________________________________________________