| previous | | | next |
| home | search | contact |
Introduction 
Advanced Topics Repository Interactions
Repositories have a notion of ``parent/child'' relationships, established at the time of the clone. When the
clone command is run, the default parent, or
parent pointer, is set to the originating repository.
Note that it's possible for a repository to be both a parent and a
child, if someone clones from a cloned repository.
Moving data between BitKeeper repositories is generally done using
bk pull
and
bk push.
These commands, by default, communicate with the parent, but data
can be shared with a repository other than the parent in a couple
of ways:
-
The
bk pullandbk pushcommands can be given an alternate_repository argument to specify a one-time change in communication. -
For multiple operations, it is possible to reset a repository's
parent by using the
bk parentcommand with an argument of the new parent. Thebk parentcommand with no argument displays the name of the parent pointer.
It's important to note that because BitKeeper has a star topology and its possible to share data with any repository, it's not necessarily recommended. The parent pointer shorthand was designed to guide the user to a defined structure for repository interactions. BitKeeper allows data to flow any direction, but in practice you don't necessarily want it that way. It's good practice to think about how the data should flow. BitMover provides consulting on this for commerical customers who have purchased 25 or more seats.
|
Home
Company
Products
How to Buy
Downloads
Contact Us
Documentation
Support
Site Map © 1997-2005, BitMover, Inc. |