DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=We/s1bgTkcJOIqf52n6r/Xuqa4wCw
	gTyW2Q/PIlL/j6S7ln2qGdhwbQI8/lpE3HLq2HyJMoGR0zAAcWihAzScm+SYXjdS
	VvSSkq4dr8v7sMCo+Ue0WL7GjjCBA5X7iqaCSXgeGsaZBaedn07OISogaqU3l+TF
	luydJ9dqF8CcJc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
From: Jim Fehrle <jim DOT fehrle AT gmail DOT com>
Date: Tue, 19 Mar 2019 22:29:50 -0700
Message-ID: <CALrWwX-qv+2pPp2ya0R3XKZg1+gHCC99tyLkRKi2KCrbGZFVBA@mail.gmail.com>
Subject: Re: Misleading timestamps on setup-x86_64.exe
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"

Date: Tue, 19 Mar 2019 19:34:38 +0100
Subject: Re: Misleading timestamps on setup-x86_64.exe
Achim Gratz writes:

> You didn't tell us how exactly you downloaded the file.  If you
> donwloaded it onto an already existing file (overwriting it), it may
> have kept the old timestamp depending on what software you used and what
> timestamp you look at.  So use a fresh directory or move the old file
> away first and see if that's helping.

Chrome renames a downloaded file if there is already a downloaded file with
the same name,
e.g. to "setup-x86_64.exe (1)".  When I tried it again now, the filestamp
showed the time it was downloaded.  Unless I see the incorrect timestamp
behavior again, it's easily reproducible and can clearly be attributed to
Cygwin, I think there's nothing to change in Cygwin.

Thanks to all,

Jim

--
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