)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"195f35adec347cb475d9509b69da7c69ba92987d","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Remove vim editor configuration from comments and add hacking checks"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This patch  does the following:"},{"line_number":10,"context_line":"* removes vim editor configuration from comments"},{"line_number":11,"context_line":"* adds hacking check [H321] for vim configuration in source files"},{"line_number":12,"context_line":"* add tests for hacking checks for vim configuration in source files"},{"line_number":13,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":6,"id":"1ae5cdf2_fb71b977","line":10,"updated":"2014-06-19 13:32:00.000000000","message":"as kyle pointed out, this part of the change is covered by other review.\n\nanyway it\u0027s better to do this (remove vim comments) and the rest (hacking check) as separate changes.","commit_id":"0d7bb7c301de932ea0b2f21ef92633b5883afa86"}],"neutron/hacking/checks.py":[{"author":{"_account_id":2592,"name":"Mark McClain","email":"mark@mcclain.xyz","username":"markmcclain"},"change_message_id":"cb0d4405c39403c4fddade04570dc195ed6abb04","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"\"\"\""},{"line_number":20,"context_line":"Guidelines for writing new hacking checks"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":" - Use only for Neutron specific tests. OpenStack general tests"},{"line_number":23,"context_line":"   should be submitted to the common \u0027hacking\u0027 module."},{"line_number":24,"context_line":" - Pick numbers in the range N3xx. Find the current test with"}],"source_content_type":"text/x-python","patch_set":6,"id":"1ae5cdf2_09755e97","line":21,"updated":"2014-06-18 20:59:21.000000000","message":"This is a general rule that should be added in upstream hacking.","commit_id":"0d7bb7c301de932ea0b2f21ef92633b5883afa86"},{"author":{"_account_id":5892,"name":"pritesh","email":"pritesh@romana.io","username":"pritkoth"},"change_message_id":"47938b1ba652427076b68b122436956e1d5c8666","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"\"\"\""},{"line_number":20,"context_line":"Guidelines for writing new hacking checks"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":" - Use only for Neutron specific tests. OpenStack general tests"},{"line_number":23,"context_line":"   should be submitted to the common \u0027hacking\u0027 module."},{"line_number":24,"context_line":" - Pick numbers in the range N3xx. Find the current test with"}],"source_content_type":"text/x-python","patch_set":6,"id":"1ae5cdf2_1f32eca6","line":21,"in_reply_to":"1ae5cdf2_09755e97","updated":"2014-06-18 21:49:55.000000000","message":"other projects have added is as project specific commandments, eg: tempest [T106], nova [N314], etc, so not sure why neutron should be an exception","commit_id":"0d7bb7c301de932ea0b2f21ef92633b5883afa86"}]}