Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<0d8d01c389c3$d68bf3b0$cd8a9dc0@uk.aonix.com>
From:	"Cliff Hones" <cliff AT aonix DOT co DOT uk>
To:	<cygwin AT cygwin DOT com>
References:	<1578FF984ABAD411AFA5000102C4BB5B04E41340 AT nimbus>
Subject:	Re: file times and cp -u
Date:	Fri, 3 Oct 2003 16:34:29 +0100
Organization:	Aonix Europe
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

> We're having a problem with 'cp -u'.  It would appear that when you copy a
> file in the manner the sub-second part of the files' timestamp gets zeroed
> out causing the file to be recopied on subsequent attempts.  Is this a bug
> in cp or is it intentional behaviour?

Are you copying to a FAT partition?  File timestamp granularity on
FAT is 2 seconds, so that would be expected behaviour.

-- Cliff


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -