Re: timestamp preservation design (issue 1256)

At 7:06 AM +0200 6/20/03, P.Marek wrote:
>- If you just have everything in the repository (sources, intermediate files,
>and output files) *and* their timestamps, you don't have a
>[clock-skew] problem with the
>build system. (At least no more than the committer).

I'm not sure I follow you here. I think, maybe, you're saying: "if
the sources, intermediates, and final files are all checked into the
repo by some tstamp-preserving system, and then all checked out again
(by the same tstamp-preserving system), then their relative
timestamps are preserved--for example, an immediate 'make' does
nothing."

This is true, but it's not the only, or even typical or most
important, situation.

Consider rather that the checkout named above might only fetch some
files; others would still be up-to-date, or perhaps locally modified.
Now, the timestamps among the freshly checked-out files are all
properly aligned, and the timestamps among those files not checked
out just now are also aligned, but the timestamps between these two
groups are not aligned.

-- 
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94015
o: 650.228.2562
c: 408.835-8090
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org