On Friday, March 03, 2000 12:41 PM, Michael R. Salazar
[SMTP:[EMAIL PROTECTED]] wrote:
> Dear CVS listers,
>
> I'm a new user of CVS and I have, what I hope, are easy questions.
> I have a rather large code that multiple users will be editing. Each
> user will need the entire code for their improvements. So, branching
> seems to make sense in this situation. My ideas are:
>
> 1. Have a centralized repository where each user can branch out of
> and create their own repository with the whole code in it.
>
Why do you want to do this? Why couldn't each user (if this is really
necessary) have their own branch inside the one repository? Or is your
definition of repository different to everyone elses, and this is what you
are trying to do.
> 2. After the individuals make their improvements, then they may
> update the centralized repository.
>
If each user has a branch, then they could merge the changes into the main
trunk.
> I don't want a repository that each user has access to and is being
> updated often by the individual users, because each user needs the whole
> code and this senario seems that it would create alot more problems with
> users attempting to commit their improvements while other users have
> checkout earlier editions. Thus, if each user had their own repository
> 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. Does this make sense? If so,
> please help with the following:
>
How will you resolve the issue of one person's changes altering the
behaviour of common material so that everyone else should get the updated
files? By using the concurrent mode of operation (without everyone on
separate branches), using good communicaiton between workers (e.g. cvs
watch) and frequent updates, you can get everyone to work together as a
team on one repository.
> 1. What are the commands for creating branches out of a repository?
>
You create a branch with a 'tag -b' command and then check it out with a
'co -r' command
> 2. How does one update a repository with another repository?
>
Can't do this, but I suspect it is not what you really want to do.
> 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
What is the problem you are trying to solve? It seems that you have
decided 'how to skin the cat' and now want some assistance. If you
describe the problem you have, people may be able to offer alternative
means of 'skinning the cat' which fit in with the way CVS works.
As other people have suggested, upgrade to 1.10.8
***************************************************************
Chris Cameron Open Telecommunications NZ Ltd
Software Development Team Leader
[EMAIL PROTECTED] P.O.Box 10-388
+64 4 495 8403 (DDI) The Terrace
fax: +64 4 495 8419 Wellington
cell: +64 21 650 680 New Zealand
Life, don't talk to me about life ....(Marvin - HHGTTG)
