[Top][All Lists]

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

RE: cvs problem

From: Jim.Hyslop
Subject: RE: cvs problem
Date: Thu, 24 Mar 2005 09:43:38 -0500

Dionysis wrote:
> Recently, I experienced problems with the cvs system. Sometimes, a
> user commits the changes of a file or adds a file to the repository,
> and then another user updates his repository, but cannot see these
> changes.
> I guess this problem may have been reported again. Any ideas about
> what the problem might be? What are the possible causes?
Hmmm... well, the description you've given is not very specific, so there
could be a great number of causes.

If I were to hazard a guess, I'd suspect that one of the people involved is
working with a "Sticky" file - either the changes were checked in on a
branch and the people who can't see the changes are on a different branch
(or the trunk), or the person/people who can't see the changes have checked
out a non-branch tag or a specific date. Use 'cvs stat' on the files that
can't see the changes, and make sure that "Sticky Date:" is "(none)" and
"Sticky Tag:" is either "(none)" or a branch tag, and make sure the branch
tag is the same one where the files were checked in.

Also, check the log ('cvs log') for the file and verify that the changes
actually made it into the repository. Use 'cvs diff -rX -rY [filename]' to
double check that the changes look reasonable (where X is the revision
before the checkin, and Y is the revision after the checkin).

Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. ( http://www.leitch.com )
Columnist, C/C++ Users Journal ( http://www.cuj.com/experts )

reply via email to

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