| Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs) | Other | rest_client.module | 2 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 6 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 7 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 8 | N/A |  |
| @see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including (). | Other | rest_client.module | 10 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 11 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 17 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 19 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 20 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 26 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 28 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 28 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 29 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 29 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 30 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 30 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 31 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 31 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 32 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 32 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 44 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 46 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 46 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 47 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 47 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 48 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 48 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 49 | N/A |  |
| @param and @return syntax does not indicate the data type. (Drupal Docs) | Other | rest_client.module | 49 | N/A |  |
| Doxygen uses @todo and @bug to markup things to be done. | Other | rest_client.module | 52 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 53 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 60 | N/A |  |
| Doxygen uses @todo and @bug to markup things to be done. | Other | rest_client.module | 62 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 68 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 73 | N/A |  |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | rest_client.module | 84 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 86 | N/A |  |
| Doxygen uses @todo and @bug to markup things to be done. | Other | rest_client.module | 89 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 93 | N/A |  |
| Separate comments from comment syntax by a space. | Other | rest_client.module | 104 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 109 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 112 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 118 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 119 | N/A |  |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | rest_client.module | 122 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 133 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 138 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 140 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 140 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 141 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 141 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 142 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 142 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 143 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 143 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 144 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 144 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 159 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 179 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 183 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 186 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 189 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 190 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 194 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 196 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 196 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 197 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 197 | N/A |  |
| Doxygen uses @todo and @bug to markup things to be done. | Other | rest_client.module | 206 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 209 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 214 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 216 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 216 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 217 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 217 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 218 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 218 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 219 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 219 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 226 | N/A |  |
| Use an indent of 2 spaces, with no tabs | Other | rest_client.module | 244 | N/A |  |
| Use an indent of 2 spaces, with no tabs | Other | rest_client.module | 245 | N/A |  |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | rest_client.module | 246 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 251 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 254 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 258 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 261 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 262 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 267 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 269 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 269 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 270 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 270 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 271 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 271 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 282 | N/A |  |
| Doxygen uses @todo and @bug to markup things to be done. | Other | rest_client.module | 288 | N/A |  |
| Doxygen uses @todo and @bug to markup things to be done. | Other | rest_client.module | 292 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 311 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 313 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 313 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 314 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 314 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 315 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 315 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 316 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 316 | N/A |  |
| do not use mixed case (camelCase), use lower case and _ | Other | rest_client.module | 318 | N/A |  |
| do not use mixed case (camelCase), use lower case and _ | Other | rest_client.module | 322 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 332 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 334 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 334 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 335 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 335 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 355 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 357 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 357 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 358 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 358 | N/A |  |
| do not use mixed case (camelCase), use lower case and _ | Other | rest_client.module | 370 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 373 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 379 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 380 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 381 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 381 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 383 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 384 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 386 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 387 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 388 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 389 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 391 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 393 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 395 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 396 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 397 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 398 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 399 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 402 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 403 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 404 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 406 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 408 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 410 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 411 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 412 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 413 | N/A |  |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | rest_client.module | 414 | N/A |  |
| do not use mixed case (camelCase), use lower case and _ | Other | rest_client.module | 418 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 424 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 428 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 453 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 455 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 455 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 456 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 456 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 457 | N/A |  |
| @param and @return syntax does not indicate the data type. (Drupal Docs) | Other | rest_client.module | 457 | N/A |  |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | rest_client.module | 461 | N/A |  |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | rest_client.module | 466 | N/A |  |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | rest_client.module | 467 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 470 | N/A |  |
| Separate comments from comment syntax by a space. | Other | rest_client.module | 471 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 476 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 478 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 478 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 479 | N/A |  |
| @param and @return syntax does not indicate the data type. (Drupal Docs) | Other | rest_client.module | 479 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 483 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 487 | N/A |  |
| Function summaries should be one line only. (Drupal Docs) | Other | rest_client.module | 493 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 495 | N/A |  |
| @param and @return descriptions begin indented on the next line. (Drupal Docs) | Other | rest_client.module | 495 | N/A |  |
| If you define a @param or @return, you should document it as well. | Other | rest_client.module | 496 | N/A |  |
| @param and @return syntax does not indicate the data type. (Drupal Docs) | Other | rest_client.module | 496 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 500 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 506 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 510 | N/A |  |
| There should be no trailing spaces | Other | rest_client.module | 517 | N/A |  |