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 
    

File and ChangeSet Comments
A quick word on comments. Unlike some source control management systems, BitKeeper requires per-file and per-cset comments. That is that each file in a changeset needs a comment as well as an overall comment for the changeset itself. Generally speaking, your per-file comments are meant to describe the actual change to that file and maybe some detail about what was changed. The changeset comment is more a summary of the overall change being committed. You will see more of why this is a good thing when we start looking back at the revision history through the revtool.
Home    Products    How to Buy    Customers    Downloads    Support    Privacy Policy    Site Map    Contact Us

© 1997-2013, BitMover, Inc.