On Tue, Sep 04, 2007 at 01:57:38PM +0100, Johannes Schindelin wrote: > Hi, > > On Tue, 4 Sep 2007, Johannes Schindelin wrote: > > > On Tue, 4 Sep 2007, Johannes Sixt wrote: > > > > > Johannes Schindelin schrieb: > > > > On Tue, 4 Sep 2007, Johannes Sixt wrote: > > > > > Therefore, I've pushed out a fixup patch at the top of mingw.git's > > > > > devel branch that converts mtime to local time > > > > > > > > On Linux, we compare to UTC to begin with, right? We should do that > > > > here, too... So if time(NULL) does not return UTC on MinGW, we have > > > > to wrap that function, too. > > > > > > According to MSDN, time(NULL) returns "the number of seconds elapsed > > > since [epoch] according to the system clock". Please don't ask me what > > > "the system clock" is. > > > > I think I know. From my QEmu adventures I know that DOS/Windows expects > > the system clock to be set to local time, in contrast to _all_ other > > operating systems. > > Now I am utterly confused. MSDN says > > FILETIME > > Contains a 64-bit value representing the number of 100-nanosecond > intervals since January 1, 1601 (UTC). > > Hmm. [Warning: war stories ahead...] If you really, really want to know more: http://search.cpan.org/~shay/Win32-UTCFileTime-1.45/lib/Win32/UTCFileTime.pm -- Rutger Nijlunsing ---------------------------------- eludias ed dse.nl never attribute to a conspiracy which can be explained by incompetence ---------------------------------------------------------------------- - 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
