anchor.diff:  
   When you commit a patch, please:
   
  -. Include the Jira issue id in the commit message, along with a short description of the change and the name of the contributor if it is not you.
  -  Be sure to get the issue ID right, as this causes Jira to link to the change in Git (use the issue's "All" tab to see these).
  +. Include the Jira issue id in the commit message along with a short description of the change. Try
  +  to add something more than just the Jira title so that someone looking at git log doesn't
  +  have to go to Jira to discern what the change is about.
  +  Be sure to get the issue ID right, as this causes Jira to link to the change in Git (use the
  +  issue's "All" tab to see these).
   . Commit the patch to a new branch based off master or other intended branch.
     It's a good idea to call this branch by the JIRA ID.
     Then check out the relevant target branch where you want to commit, make sure your local branch has all remote changes, by doing a +git pull --rebase+ or another similar command, cherry-pick the change into each relevant branch (such as master), and do +git push <remote-server>
  
positive.code: Under the _dev-support/_ folder, you will find _hbase_eclipse_formatter.xml_.
  We encourage you to have this formatter in place in eclipse when editing HBase code.
  
  .Procedure: Load the HBase Formatter Into Eclipse
  . Open the  menu item.
  . In Preferences, Go to `Java->Code Style->Formatter`.
  . Click btn:[Import] and browse to the location of the _hbase_eclipse_formatter.xml_ file, which is in the _dev-support/_ directory.
    Click btn:[Apply].
  . Still in Preferences, click `Java->Editor->Save Actions`.
    Be sure the following options are selected:
  +
  * Perform the selected actions on save
  * Format source code
  * Format edited lines
  +
  Click btn:[Apply].
  Close all dialog boxes and return to the main window.
  
  
  In addition to the automatic formatting, make sure you follow the style guidelines explained in <<common.patch.feedback,common.patch.feedback>>
  
  Also, no `@author` tags - that's a rule.
  Quality Javadoc comments are appreciated.
  And include the Apache license.
  
  [[eclipse.git.plugin]]
  ==== Eclipse Git Plugin
  
negative.code: [[code.standards]]
  === Code Standards
  
  
  ==== Interface Classifications
  
  