[Top][All Lists]

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

Re: Problems with update -C

From: Mark E. Hamilton
Subject: Re: Problems with update -C
Date: Fri, 09 Sep 2005 09:52:45 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913


Jim Hyslop wrote:
Mark E. Hamilton wrote:


We're having some odd problems with 'cvs update -C'; it reports as locally modified (and hence backs up) files that are not modified in the working directory. If I diff the '.#' backup of the file with the version updated from the repository there area no differences. (Additionally, I had done a 'cvs -qn update' in the same working directory just prior to the update that had this error, and no files were reported as being out-of-date.)

It also reports as locally modified files that were updated in a previous commit, even though they were not modified in the working directory either. (They were committed from somewhere else.)

This sounds like something might have changed the timestamp of the file, without changing the contents. If this happens again, compare the timestamp on the file with the timestamp stored in CVS/Entries. A simple "cvs update" usually sets everything right.

Rats. That's exactly what's happening.

Is it intentional that 'cvs update' and 'cvs update -C' behave differently in this case? Assuming that the only difference is that the file has been touched, 'update' reports nothing about the file and 'update -C' tries to update it. I had expected that they would work the same way, ie, only refresh the files from the repository if it was actualy changed.

Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.

reply via email to

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