previous | next
 
home  |  sales  |  customers  |  jobs  |  contact  |  search  
 
 Home 
 Products 
 Customers 
 Comparisons 
 Sales 
 Test Drive 
      - Installation 
      - Setting Up the Demo Repo 
        . Cloning a Remote Repo 
        . Cloning a Local Copy 
      - Pull Changes from a Parent 
      - Making Changes 
        . Checking out files 
        . Modifying and creating files 
        . Viewing Changes 
        . Committing Changes 
      - Using Revtool 
        . Launching Revtool 
        . Looking at a Changeset 
        . Looking at a file 
      - Merging Changes 
        . Pulling and Resolving a Conflict 
        . Merging a file 
        . Committing a Merge 
      - Pushing Changes Back to the Parent 
      - Extra Credit Work 
        . Checkout Modes 
        . File and ChangeSet Comments 
 Company 
 Jobs 
 Support 
 Documentation 
 Search 
 Site Map 
    

Cloning a Local Copy
You've just cloned a remote repo to your local system, and we're ready to work! Notice that BitKeeper has placed an overlay icon on the folder to show that this is a BitKeeper repository. When working within the Explorer plugin, BitKeeper uses several icon overlays to give you an idea of what you're looking at with a glance.

Now, this demo repo was cloned from bkbits.net, and we don't have permission write back to the parent repository, so the next thing we want to do is make another clone of our new repo to the same directory so that we can make some changes.

Right-click on the white background of your Explorer window.
Click BitKeeper -> Clone this Repository...


You'll see the familiar clone dialog pop up. Notice that the dialog has already filled in the name of the repo we are cloning and a suggestion for the copy of the repo. We'll just keep the defaults for now and make a new bk_demo_copy directory to play in. You will see the command window fly by again as the repo is copied. Once it's done you can close the command window, and your directory should look like this:


You should now have a directory with two repos: bk_demo and bk_demo_copy. Each repo knows about where it came from and who its parent is. bk_demo_copy knows that bk_demo is its parent, and that's where it will pull its updates from and send its changes to. bk_demo knows that http://bkdemo.bkbits.net/bk_demo is its parent, and that is where it will pull updates from.

Next Step: Pulling changes from a parent


Home    Products    How to Buy    Customers    Downloads    Support    Privacy Policy    Bug DB    Site Map    Contact Us

© 1997-2011, BitMover, Inc.