previous | next
 
home  |  sales  |  customers  |  jobs  |  contact  |  search  
 
 Home 
 Products 
 Customers 
 Comparisons 
 Sales 
 Test drive 
 Company 
 Jobs 
 Support 
 Documentation 
      - Quick reference guide 
      - Reference manual 
      - Command Comparisons 
        . CVS to BK 
      - Bug Database 
        . Submitting Bugs 
        . Querying Bugs 
        . Viewing Bugs 
        . Updating Bugs 
      - User guide 
      - FAQS 
        . General usage 
        . Making changes 
        . Viewing changes 
        . File operations 
        . Multiple file operations 
        . Merges 
        . Import 
        . Undoing work 
        . Tags 
        . Failure recovery 
        . Event triggers 
        . Configuration 
        . Error messages 
        . Windows/NT 
        . BK/Web 
        . Linux 
      - HOWTO's 
        . License Keys: Closed Source 
        . License Keys: Open Source 
        . Multiple code lines 
        . CVS to BitKeeper 
 Search 
 Site Map 
    

Tags


  • How do I label revisions of a package? And how do I then retrieve a certain package revision by label in case one labeled version works and the other does not?
    Labels are called "tags" in BitKeeper. To add a tag to the package, make sure you've checked in everything and created a changeset. You can use bk status to see what needs to be checked in and/or committed to a changeset. Tag the tree by typing:

    bk tag TagName

    The most recent changeset is now labeled, or tagged, with "TagName". If you didn't want to tag the most recent changeset, you can say

    bk tag -r<vers> TagName

    to add the name to any revision. You can now use this tag as an argument to clone, for example:

    bk clone -rbeta master beta

    which creates a repository called "beta" that has everything up to and including the "beta" changeset.

    
    
    A frequent problem is that you tag a changeset with "Done" and
    then discover you weren't really done.
    You can update the tag to the later changeset by running the
    bk tag Done command again.
    
    
    
    
  • How do I view comments that have been written for specific files or a labeled package?
    For individual files, use bk prs filename. For a tagged changeset, use bk changes.
    
    
    
  • Is there an easy way to find out what tags are in a tree and when they were created with what changesets, etc.?

    bk changes -t

    or

    bk -R prs -hr1.0.. -nd'$if(:TAG:){:DEFAULT:}' ChangeSet


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

© 1997-2007, BitMover, Inc.