[Top][All Lists]

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

Re: Timestamp handling in checkout vs update

From: Donald Sharp
Subject: Re: Timestamp handling in checkout vs update
Date: Mon, 7 Jan 2002 19:40:36 -0500
User-agent: Mutt/1.2.4i

On Mon, Jan 07, 2002 at 04:13:46PM -0800, Harper, Don wrote:
> I have observed and read in the archives that cvs sets file timestamps to
> the commit times when doing a checkout operation but sets them to the
> current time when doing an update.  What is the rationale for this? 

Suppose file foo.c.  Which creates foo.o. and ultimately foo
Suppose the date is today.

foo.c version 1.2 date stamp in repository is 12/1/01
foo.c version 1.1 date stamp in repository is 1/1/01

While your local copy version 1.1 date stamp is from 12/15/01.

You have compiled foo.o and foo.  With time stamps on 12/16/01.

Now suppose you update foo.c to version 1.2.

Under your proposal the timestamp would be set back to 12/1/01
for foo.c Thus making make systems think the foo.o and foo files
do not need recompilation.  

Under the current mechanism.  foo.c gets todays date time stamp 1/7/02.
The make system sees that foo.c is newer than foo.o and foo.  Thus
a rebuild is needed.


> It seems
> to me that operations such as 'update -C' should set the timestamp back to 
> the commit time just like checkout.
> Any information would be greatly appreciated.
> Don Harper
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

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