There's one more thing you might want to do if you're part of a larger group that wants to experiment with bitkeeper on the same remote, parent repository and that's to make your own local tracking repository. A tracking repository (and I'm hoping I'm using the terminology correctly) is just a clone of the remote repo of interest, from which you'll make additional local clones. It's just an extra level of clone so that you always have a local, good, undamaged copy of the remote repo, just in case you make a mess of yours.

As an example of setting up a tracking repo and a local repo off of that:

 $ bk clone     # tracking repo
 $ cd <somewhere else>
 $ bk clone file:///<absolute path to tracking repo> <dirname>
You now have your own copy of the repo that you can trash to your heart's content, and which you can delete and reclone at will.

To keep up to date, you'll run bk pull twice:

  1. Update the tracking repo.
  2. Update your local repo off of that.

Note that you don't need to do any checkouts in the tracking repo; just leave everything in the SCCS-managed directories in that repo and do the checkouts in your local clone. In the simplest case, the only things you'll ever do with the tracking repo is update it, and update from it, at least for now.

If you didn't understand any of the above, don't worry about it.

This topic: Dev > WebHome > BitKeeperNotes > BkTrackingRepo
Topic revision: r3 - 2004-11-04 - 19:05:16 - RobDay
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback