Reviewing and Checking In

As your work achieves intermediate milestones, it is a good idea to check it in, rather than waiting until it is all done and checking everything in at once. Checking in your files frequently enables you to step back from misfortunes, and provides you with a logical sequence--especially handy when you are making complex changes.

A good review consists of the following steps:

• First, here are a few tools which will make your work a little simpler:
  
  
• You should examine all your edits, to make sure you haven't introduced unintentional differences in the files. To do this, you can feed the list from lsbranch to ctdiff:
  
  5% ctdiff -brpoint -graphical `lsbranch wilder_ROCei21028`
  
  
• If you have not already checked in all your changes, this command will check-in all checked-out files in your view, using the comments that you originally supplied at check-out. Files with no changes will be ignored:
  
  5% cleartool ci -nc `cleartool lsco -avobs -cview -short`
  
  
• Next, remove all checked-out but unchanged files, and empty (containing only version zero) branches:
  
  6% cleartool unco `cleartool lsco -avobs -cview -short`
  7% /packages/cc_site/bin/rm_empty_branches -all wilder_ROCei21028
  
  

This completes your review of your work. You are now ready to submit the changes to Peer Review.

Return to SCM Std Ops page