BitKeeper - The Scalable Distributed Software Configuration Management System

By default, BitKeeper operates in a "clean" checkout mode. This means that all files must be explicitly checked out in either read-only or read-write mode. You can specify that a particular repository should be in "checkout: get" or "checkout: edit" mode as well as specify in your own configuration what the default mode should be.

Available Checkout Modes

checkout: get
In get mode, BK will automatically checkout each file in read-only mode (using bk co ) after doing a checkin.

checkout: edit
In edit mode, BK will automatically checkout each file in read-write mode (using bk edit ) after doing a checkin.

checkout: last
In last mode, BK will preserve the state of the file before checkin.

checkout: none
In none mode, BK will clear the file after doing a checkin. This is the default.

The repositories we are using for this test drive have been marked "checkout: get" which means that all files within the repo will be checked out in read-only mode by default. That's why we have to first checkout the files for editing before we can make any changes to them. In most cases you will usually just checkout the files you plan to modify for editing and leave the rest as read-only as it makes it really easy to see what you're changing from the Explorer. If you were to run in "checkout: edit" mode, all of the files would already be in the directory and writable after a clone, and you could skip the step of having to check them out.

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