In the most common model of BitKeeper usage, you'll most likely do some or all of the following things:

  • select some package whose source you want to work with
  • find a repository with a copy of that package, and clone that repository, so that you have a child copy of that parent repo
  • check out or edit some of the files in your copy, depending on whether you want to just examine some of the source files, or whether you want to make some local changes
  • save the changes you want to your local source files
  • when you think you're happy with the changes to one of your source files, you can check in your copy of that file back into your local repo
  • do other standard filesystem operations like create new files, delete existing files, and rename and move files and directories
  • edit, modify, save and check in changes to as many files as you want until you're happy with that collection of changes, then commit that set of changes to a new change set in your repo
  • occasionally, depending on how much you want to interact with your parent or other repos of the same package, you might pull updates from your parent, or push your changes to your parent or other repos to keep everyone up to date

Got all that? For more detailed definitions of some of the above terms, continue on to BkTerminology.

This topic: Dev > WebHome > BitKeeperNotes > BkOverview
Topic revision: r2 - 2009-07-04 - 13:44:11 - KapilaBogahapitiya
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2019 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