| Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs) | Other | user_history.module | 2 | N/A |  |
| Menu item titles and descriptions should NOT be enclosed within t(). (Drupal Docs) | Other | user_history.module | 34 | N/A |  |
| Menu item titles and descriptions should NOT be enclosed within t(). (Drupal Docs) | Other | user_history.module | 35 | N/A |  |
| There should be no trailing spaces | Other | user_history.module | 77 | N/A |  |
| indent secondary line of comment one space | Other | user_history.module | 94 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | user_history.module | 126 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | user_history.module | 126 | N/A |  |
| indent secondary line of comment one space | Other | user_history.module | 127 | N/A |  |
| indent secondary line of comment one space | Other | user_history.module | 144 | N/A |  |
| indent secondary line of comment one space | Other | user_history.module | 156 | N/A |  |
| The $message argument to watchdog() should NOT be enclosed within t(), so that it can be properly translated at display time. | Other | user_history.module | 167 | N/A |  |
| indent secondary line of comment one space | Other | user_history.module | 180 | N/A |  |
| indent secondary line of comment one space | Other | user_history.module | 197 | N/A |  |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | user_history.module | 201 | N/A |  |
| indent secondary line of comment one space | Other | user_history.module | 209 | N/A |  |
| indent secondary line of comment one space | Other | user_history.module | 231 | N/A |  |
| Function documentation should be less than 80 characters per line. | Other | user_history.module | 245 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | user_history.module | 245 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | user_history.module | 246 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | user_history.module | 246 | N/A |  |
| Separate comments from comment syntax by a space. | Other | user_history.module | 264 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | user_history.module | 277 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | user_history.module | 277 | N/A |  |
| indent secondary line of comment one space | Other | user_history.module | 278 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | user_history.module | 300 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | user_history.module | 300 | N/A |  |
| indent secondary line of comment one space | Other | user_history.module | 301 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | user_history.module | 330 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | user_history.module | 331 | N/A |  |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | user_history.module | 334 | N/A |  |