[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: File date and timestamp

From: Jim.Hyslop
Subject: RE: File date and timestamp
Date: Tue, 29 Jun 2004 09:49:41 -0400

Flagg, David wrote:
> The reason the timestamp is important is because the file is 
> part of an external delivery.  the customer has previous 
> deliveries and flags files whose timestamps have changed.  As 
> a result, they wonder why the timestamp changed on this 
> binary file, yet we didn't inform them of any changes with 
> that particular capability.
Ah, I see. I was under the impression that the library was provided to you
from a third party.

Well, that just points out the fragility of depending on timestamp alone to
tell you whether or not something has changed. Are the MD5 checksums the
same for both versions? If so, then the file has only been 'touched' not

Storing final object code in CVS is generally considered not a good
practise. If you've been following the "CVS corrupts binary files" or "FUD"
threads (and can separate the wheat from the chaff in those threads) you'll
see what I mean.

Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (
Columnist, C/C++ Users Journal (

reply via email to

[Prev in Thread] Current Thread [Next in Thread]