[ On Thursday, March 2, 2000 at 16:40:47 (-0700), Michael R. Salazar wrote: ]
> Subject: new guy - hopefully easy questions
>
> 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.
Unfortunately you're assuming too much of CVS. It cannot directly
integrate operations on more than one repository.
While there are approaches you could use to do this kind of thing
they'll all require a bunch of extra work be done in order to move
changes from one repository to another.
Assuming CVS is the right tool for your requirements other than this
issue you should ideally try for building just one centralised
repository and always have everyone work from it directly.
> 2. How does one update a repository with another repository?
This is where the prolem with your plan lies.
So far as I'm aware there's only one way to do this: Manually.
I.e. you would have to commit each change to the central repository.
Obviously it would be possible to write a front-end that could automate
this process, but I don't know of any such tool currently available.
The only other version control tool that I know of that's readily able
to easily copy change sets from one repository to another is BitKeeper.
(www.bitkeeper.com)
> As you all can probably tell by these questons, don't assume too much in
> your answers. If possible, please provide the necessary commands and a
> brief description. The architecture on which I am running is SGI Irix
> 6.5. I'm using CVS version 1.9
You should really update to the latest patch release (1.10.8 I think).
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
