Your first step in working with a remote repository is to "clone" a copy of it to your local system with, say:
 $ bk clone mykernel
The above will clone that bk repository into the directory named, in your case, mykernel. By default, the directory name will match the repository name, so it's your choice if you want to use a different name.

Once this is done, you can enter your new directory with:

 $ cd mykernel
and you'll notice that there are (typically, but not always) no visible files -- everything is initially stored in SCCS directories, and you'll need to "check out" or "edit" files to get at them. More on that shortly.

There are a number of ways you can identify a remote repository; check under bk helptool url for the possibilities.

Advanced: If you're feeling ambitious, you can clone a specific snapshot of a remote repo using the -r option, with one of these possibilities:

 -r<cset rev number>
 -r<cset key>
 -r<tag name>

But, for now, you'll probably just want the default, most recent version.

This topic: Dev > WebHome > BitKeeperNotes > BkClone
Topic revision: r5 - 2004-11-05 - 10:41:36 - RobDay
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2020 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