From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33941 invoked by alias); 20 Mar 2019 05:30:39 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 33655 invoked by uid 89); 20 Mar 2019 05:30:21 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=attributed, H*c:alternative X-HELO: mail-ed1-f43.google.com Received: from mail-ed1-f43.google.com (HELO mail-ed1-f43.google.com) (209.85.208.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 20 Mar 2019 05:30:05 +0000 Received: by mail-ed1-f43.google.com with SMTP id q14so864778edr.5 for ; Tue, 19 Mar 2019 22:30:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Rn1FrT5ErdzkL+BJr9uJfxJEJeOU8N1PRM9P0e5PTPU=; b=eKrmN4LbcwtBem5lRwY60oLhaqbn0cGFlvQbJVCaLuQo0IQyi2vXWd51T3JVB9NZ4C 4eLWcjbyph3IrPmd9mxiaV9twJ/Uv30bQYkptKylt49463hmcSICK/ifE8rB9zrTDy6+ fFvtzZlM3lQwFoul8dGxdmxZ74pt8MgvgpCgrbKp2JtJ8m+sPYL+miAOmx8aBxXuhaql G48d4gKsLIt3LfYM1vQ4rBQL1h/h1cJfDP+C1QKIvpAi3fH13EaO7its1w7bjwdXSkMb LoV/uN88TH+zWhFWJkZRLL8HlQOsDqiFg8Jw3Efjy++XHwrgxfig7XcLOXNxN+CQ7sAh I9DA== MIME-Version: 1.0 From: Jim Fehrle Date: Wed, 20 Mar 2019 05:30:00 -0000 Message-ID: Subject: Re: Misleading timestamps on setup-x86_64.exe To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-03/txt/msg00503.txt.bz2 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