Re: Pbm updating sandbox

[Todd Denniston]

Muriel Delaveau wrote:
> 
> Hello,
> An user has put a new source in the repository.
> But other users can't even see the new source when updating their
> sandbox even which tkcvs.
> 
> What can be the reason ?
> 
> Thanks for your help.

Assumption, the user who "put the new source in the repository", did so by
using `cvs add file` and `cvs commit file`, and there is a ,v for the file
in the repository.

Q1) is the new file in a new directory, or a directory that never had any
thing in it before?
Reason they don't see it: their sandbox has been optimized to work on what
was known at the time of their checkout, i.e., don't waste time looking for
things we did not find the first time.
Fix, have every one else `cvs update -dP`.

Q2) is the user who "put the new source in the repository", working on a
branch, or a different branch from the rest of the users (the trunk can be
considered a branch for consideration of this question)? 
Reason they don't see it: branches exist for work separation and segregation
of changes so one group will not affect another until they are ready to be
affected.
Fix, read the CVS manual on merging changes from branch to branch. (-j
options to update or checkout, IIRC)

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter