Hello, and no problem at all.
> It's a bit surprising that it works because docs say that _utime() and
> _futime() are identical except that _futime() takes a file descriptor.
You're right, that shouldn't help if close() was consistent... apparently it
only resets the timestamp when no utime was m
Hello and sorry for taking so long to reply.
On 2016-04-28 Martok wrote:
> xz when built for Windows with gcc on mingw32 or mingw-w64 does not
> preserve timestamps. I have found that this is because MinGW only
> provides utime() with filename as target, and this means that the
> file time is adju
Hello List,
xz when built for Windows with gcc on mingw32 or mingw-w64 does not preserve
timestamps. I have found that this is because MinGW only provides utime() with
filename as target, and this means that the file time is adjusted by
io_copy_attrs() and then immediately reset to 'now' when the
