)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":12395,"name":"Roman Vasylets","email":"pomeo92@gmail.com","username":"rvasilets"},"change_message_id":"70e8b0cf7e4b89267e9eccb4552938c298ad86c6","unresolved":false,"context_lines":[{"line_number":9,"context_line":"Some tests used incorrect order assertEqual(observed, expected)."},{"line_number":10,"context_line":"The correct order expected by testtools is"},{"line_number":11,"context_line":"assertEqual(expected, observed)."},{"line_number":12,"context_line":"This patch includes a few of the files changed to ease the review."},{"line_number":13,"context_line":"The other files will be committed in the coming patches."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Change-Id: Ib155e5720cc7dcd0adadc0e0000a7e6aef1ba9bc"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3ac371cc_498b7ac3","line":12,"updated":"2016-08-17 16:08:39.000000000","message":"Review will be not too hard. So fill free to make bigger patch. If it is too big then we don\u0027t want to see 10 patches in git history  with title \u0027Fix order of ...\u0027 At least we have 500(good to have, not required) lines as an upper bound per patch. I\u0027d prefer to see all such fixes in one patch","commit_id":"ccdcd63453e041fe759a26a1d5ae0fe4041d7fc5"}]}
