From: Jim Fehrle <jim.fehrle@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Misleading timestamps on setup-x86_64.exe
Date: Wed, 20 Mar 2019 05:30:00 -0000 [thread overview]
Message-ID: <CALrWwX-qv+2pPp2ya0R3XKZg1+gHCC99tyLkRKi2KCrbGZFVBA@mail.gmail.com> (raw)
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
next reply other threads:[~2019-03-20 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 5:30 Jim Fehrle [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-19 0:28 Jim Fehrle
2019-03-19 4:39 ` Mark Geisert
2019-03-19 5:18 ` Brian Inglis
2019-03-19 18:34 ` Achim Gratz
2019-03-18 6:04 Jim Fehrle
2019-03-18 8:55 ` Mark Geisert
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=CALrWwX-qv+2pPp2ya0R3XKZg1+gHCC99tyLkRKi2KCrbGZFVBA@mail.gmail.com \
--to=jim.fehrle@gmail.com \
--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).