public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: akiki@free.fr
To: cygwin <cygwin@cygwin.com>
Subject: Cygwin DLL 3.2.0 (W10) Problem with touch (8.26)  for old dates < 1970
Date: Wed, 14 Apr 2021 12:36:14 +0200 (CEST)	[thread overview]
Message-ID: <603461978.103298236.1618396574434.JavaMail.root@zimbra76-e14.priv.proxad.net> (raw)
In-Reply-To: <369474148.103071581.1618392198922.JavaMail.root@zimbra76-e14.priv.proxad.net>

Hi, 
I encountered problems with the use of timestamps in cygwin. 
May be it's an old problem, I don't know, using essentially files "recently" created/modified. 


I want to say after 1970 No problem, but before ... 


To day: 
touch -m -t 190001011200.00 x gives touch: format de date « 190001011200.00 » incorrect 
touch -m -t 190101011200.00 x gives ok - with ls -l x: 
-rw-r--r-- 1 user group 0 1 janv. 1910 x 


touch used is well /bin/touch 


By comparison on Ubuntu 18 LTS 
touch -m -t 190001011200.00 x is correct 


I know, timestamps are managed differently in windows and linux. 


I see also with the new windows terminal with ubuntu 
On windows file, like /mnt/c/x (windows is mounted by linux) 
touch -m -t 190001011200.00 x ; echo $? gives 
0 #No error but timestamp is set to 1970-01-01 
On linux file as ~/x, it's correct; 


So, which confidence to have with cygwin about files of timestamp 19xx before 1970. 
May be it's ok after 1901. The answer is NOT. 
touch -m -t 190101011200.00 x gives sometimes format de date incorrect 


In some windows directories and more problematic, for a same directory, I don't understand why. 
May be due to embedded mounts. 


I hope to have been clear enough. 



Thanks for answers.

       reply	other threads:[~2021-04-14 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <369474148.103071581.1618392198922.JavaMail.root@zimbra76-e14.priv.proxad.net>
2021-04-14 10:36 ` akiki [this message]
2021-04-14 11:16   ` Thomas Wolff
2021-04-14 13:54   ` Lee
2021-04-14 15:25   ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=603461978.103298236.1618396574434.JavaMail.root@zimbra76-e14.priv.proxad.net \
    --to=akiki@free.fr \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).