Philippe <jwphubert <at> gmail.com> writes: > I've found an interesting behaviour with this command on my Windows 7 64bits > system. It seems that there is a bug, or that we should change the > documentation... But I can get around with the following date/time format: > > MMddhhmmyy > > where > > MM: Month (01-12) > dd: day (01-31) > hh: hours (00-23) > mm: minutes (00-59) > yy: 2 digit year > > yy is interesting. 00 to 37 yields 2000 to 2037. 70 to 99 yields 1970 to > 1999. 38 to 69 leaves the date unchanged, even for new correct time, day or > month. > > hh has another twist. It will change time an hour MORE than what specified on > the command line. If you want the file date to be 9AM, you enter 08. Another > twist, if you specify 1231235511, the file date will be 2012 dec 31, 00h55, an > hour later than the one specified. > > Philippe > > Sorry, little mistake. On my previous post, your should read:
"Another twist, if you specify 1231235511, the file date will be 2012 jan 01, 00h55, an hour later than the one specified." -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
