X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Cc: Corinna Vinschen Message-Id: From: Denis Excoffier To: cygwin@cygwin.com In-Reply-To: <20100317115612.GH6505@calimero.vinschen.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: modification time of standard input is wrong Date: Wed, 17 Mar 2010 19:15:41 +0100 References: <20100317115612.GH6505@calimero.vinschen.de> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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. Regards. Denis Excoffier. -- 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