On Thursday 2 March 2000, at 16 h 40, the keyboard of "Michael R. Salazar"
<[EMAIL PROTECTED]> wrote:
> 1. Have a centralized repository where each user can branch out of
> and create their own repository with the whole code in it.
>
> 2. After the individuals make their improvements, then they may
> update the centralized repository.
Basically, CVS is not able to have more than two levels (the user's working
directory and the Repository). Hierarchical repositories are not a feature of
CVS.
> I don't want a repository that each user has access to and is being
> updated often by the individual users,
This is a policy matter, not a technical one. CVS is policy-free. Some
organizations say to their contributors "commit as soon as you changed a
comma", other say "commit *only* when you are *sure* you didn't break the f...
thing".
More technically, commit rules could say "thou shall commit only code that
compiles" or "thou shall commit only code when you recompile the whole project
and pass the whole regression test".
> and checkout and commited as necessary, this wouldn't be a problem. The
> problem will come when the users attempt to update the centralized
> repository, but this won't be that often.
Again, "often" depends on your commiting rules, not on CVS.
