This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.5.25: bug in touch statement
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 15 May 2011 13:30:55 -0400
- Subject: Re: 1.5.25: bug in touch statement
- References: <415512198.1687271301267190457.JavaMail.root@zimbra6-e1.priv.proxad.net> <277043603.1687291301267204451.JavaMail.root@zimbra6-e1.priv.proxad.net> <871v1scd5c.fsf@navakl084.mitacad.com> <loom.20110515T134854-740@post.gmane.org>
- Reply-to: cygwin at cygwin dot com
On Sun, May 15, 2011 at 12:09:01PM +0000, Philippe wrote:
>Toby Allsopp <Toby.Allsopp <at> navman.co.nz> writes:
>> On Mon, Mar 28 2011, andre wrote:
>> > I can't do on cygwin 1.5.25 :
>> > $ touch -t 201103270200 file
>> > touch: format de date invalide `201103270200'
>> >
>> > nor this equivalent : $touch -t 03270200 file
>> >
>> > It's very surprising , but ...
>> > If I change 27 for 28 it's OK - idem if i change 2011 by 2010...
>>
>> I would guess this has something to do with the transition to daylight
>> saving time, which happened at 0200 on 2011-03-27. This means that the
>> time you are specifying didn't ever exist (in your local time zone)
>> because 0200 became 0300.
>>
>> Perhaps you can get what you want by specifying the time in UTC?
>>
>>
>I've found an interesting behaviour with this command on my Windows 7 64bits
>system. It seems that there is a bug, or the we should change the
>documentation... But I can get around with the following date/time format:
Cygwin 1.5.25 is not going to be changed. What you see is what you get.
--
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