| previous | | | next |
| home | search | contact |
Introduction 
Getting Started Cloning A Repository
If the previous mentioned setup example happened to be a single-developer project, that might be the only repository necessary. The developer would simply work in the master repository. Most projects, however, are multi-developer projects and therefore the master repository would be cloned for each developer on the team. After the first repository is created, subsequent copies of that repository are created using
bk clone.
It's important that bk clone is used to make copies of the
repository, and that bk setup is not run more than once,
since bk setup generates a project key, but bk
clone copies the existing key, and each project needs one
unique instance of the key.
The bk clone command makes a local copy of the master
repository, which is also known as the ``parent'' repository.
The repositories then have a parent-child relationship, and
subsequent BitKeeper operations use the knowledge of this
relationship.
It is possible to specify a new parent with bk parent to
change the location of the effects of a BitKeeper command.
|
Home
Company
Products
How to Buy
Downloads
Contact Us
Documentation
Support
Site Map © 1997-2005, BitMover, Inc. |