[Octave-bug-tracker] [bug #64933] Stat sometimes produces wrong timestamp

[INVALID.NOREPLY]

Follow-up Comment #4, bug #64933 (project octave):

To be honest, I'm not sure how Windows handles timestamps. However, after
changing the timestamp with the posted powershell command, the timestamp shown
in the Windows File Explorer is the same as the one I handed over as a string.
Therefore, the mtime value consistent with that string and the Windows
timestamp is the one with the fid.

So I only know that the powershell command is coherent with the system's
handling of timestamps - as I would expect. However, I'm not sure if there is
any time zone conversion happening in the background.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64933>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/