tag 11798 notabug
thanks

On 06/27/2012 03:52 AM, Patrick Castet wrote:

> $ touch a0.a
> $ touch -d "20000102 03:04:05" a0.a

Thanks for the report.

> if you check with widows  cmd, you get 

I assume you meant Windows, not widows.

> 
> a0.a is dated with  20000102 04:04
> 
> 
> wich is not correct !

Welcome to the joys of Microsoft's decision to store file timestamps
with respect to local timezones rather than with respect to UTC, even
though that means that physically relocating your machine to a spot with
different daylight savings rules renders those timestamps ambiguous.
The difference of one hour that you are seeing is due to Windows'
insistence on applying a (possibly wrong) daylight savings adjustment,
based on the timestamp on the file vs. what Windows considers as your
current time zone.

Furthermore, since this is an issue that you noticed with the cygwin
port of coreutils, you might be better off asking on the cygwin list.
Perhaps they will agree, and consider this a bug in cygwin1.dll for
converting timestamps in the futimens() and or stat() functions into
file timestamps in a manner inconsistent with Windows daylight savings
gyrations; but more likely the cygwin folks will state that there is
nothing that can be done about the mismatch in opinions on how daylight
savings affect Window file time stamps.

At any rate, this is a Windows or cygwin issue, not an upstream one, so
I'm closing out this upstream bug as a non-issue.

-- 
Eric Blake   eblake@redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org