)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7233,"name":"Matthew Oliver","email":"matt@oliver.net.au","username":"mattoliverau"},"change_message_id":"2b198de579c0048cdc11a3e804ae99bca65a90a2","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     zheng yin \u003cyin.zheng@easystack.cn\u003e"},{"line_number":5,"context_line":"CommitDate: 2016-08-23 14:39:40 +0800"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Improve code readability"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Fox example: assertTrue(a in resp.headers and"},{"line_number":10,"context_line":"                        b in resp.headers and"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"1ac06dbe_136978f9","line":7,"updated":"2016-08-24 01:31:52.000000000","message":"This commit message is a little too broad, from it I can\u0027t tell the extend on the review. Unless of course test/unit/obj/test_server.py is the only place that code readability can be improved. The commit message needs to give the scope of the patch. As once it\u0027s merged it\u0027ll be the only thing used to reference this change in the git repository history.\n\nThe example is great, but maybe it could start with something like:\n\n  Improve readability in the obj server\u0027s unit tests\n\n  This change improves the readability of the object-server\u0027s unit\n  tests by breaking down some long assertTrue statements into smaller\n  and much easier to read and more relevant assert statements.\n\n  For example:\n    assertTrue(a in resp.headers and\n               b in resp.headers and\n               c not in resp.headers)\n\n  Is equal to:\n\n    assertIn(a, resp.headers)\n    assertIn(b, resp.headers)\n    assertNotIn(c, resp.headers)","commit_id":"f038fd710231b32ecbbd4d9c5f2af6a55e2d838d"}]}