X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 17 Mar 2010 19:24:54 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: modification time of standard input is wrong
Message-ID: <20100317182454.GV6505@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <F724F0A6-4415-4BCA-BF3D-D3BBA25B32DA AT free DOT fr>  <20100317115612 DOT GH6505 AT calimero DOT vinschen DOT de>  <F46DE894-8A72-4B8B-A610-68D9E059816D AT free DOT fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F46DE894-8A72-4B8B-A610-68D9E059816D@free.fr>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Mar 17 19:15, Denis Excoffier wrote:
> 
> On Wed, Mar 17, 2010 at 12:56:12PM +0100, Corinna Vinschen wrote:
> >>
> >> What impact?  I don't think there is any standard which requires
> a non
> >> filesystem based stream to have a current timestamp and a tool
> relying
> >> on that might be broken.  All our streams which are not backed by a
> >> filesystem w/ valid timestamps have an artificial timestamp of
> >> 2006-12-01 00:00:00.
> The file `algorithm.doc' within the gzip distribution states that
> "If input does not come from a regular disk file, the file
> modification time is set to the time at which compression started.".
> 
> This has been reported to the `bug-gzip' mailing list (see
> http://lists.gnu.org/archive/html/bug-gzip/2010-03/msg00000.html).
> In his answer, Eric Blake suggested that the bug might be in
> cygwin1.dll.

The quote does not imply that the input has to have that modification
date.  It only implies that the modification date of the output file
of the compression is set to the time the compression started.  That
has nothing to do with the timestamp of the input stream.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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