previous | next
 
home  |  search  |  contact  
 
 
 Introduction 
 BitKeeper Concepts  
 Getting Started  
 Advanced Operations 
      - Resolving Conflicts  
        . When is a Resolve is Needed?  
        . Resolve 
        . Merging Content Conflicts  
      - Specifying Older Revisions 
        . File level 
        . ChangeSet level 
        . Tag level 
      - Tags  
        . Creating a Tag 
        . Updating a Tag 
        . Revert to a tree as of Tag 
      - Branching  
        . When to Create a Clone 
        . How to Enforce Work Flow 
        . Branching and Merging 
      - Revision Ranges 
        . Specifying by Revisions 
        . Specifying by Dates 
        . Revision and Date 
      - Remote repositories 
        . bkd 
        . Sending Changes via Email 
        . Receiving Changes via Email 
 Advanced Topics 
 Reporting and Data Mining  
 Appendix A: Installation 
 Appendix B: Administration 
 Site Map 
    
Resolve
When a pull does not succeed due to conflicts, to resolve those conflicts, run:

bk resolve

You will be prompted for each type of conflict for each file. For each type of conflict there are available actions you can take, to see a list of available actions hit:

enter

For file content conflicts use the file merge tool by hitting:

F

Resolve all the conflicts in the file merge tool and save.

You will be back at the resolver prompt. If there are more files to merge, do those. If there aren't any more files to merge, commit the merges to a changeset by hitting:

C

While it is OK to quit out of resolve without finishing, the repository will be locked and remain locked until you return to resolve and finish up the merge process.


Home    Company    Products    How to Buy    Downloads    Contact Us    Documentation    Support    Site Map

© 1997-2011, BitMover, Inc.