)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7233,"name":"Matthew Oliver","email":"matt@oliver.net.au","username":"mattoliverau"},"change_message_id":"70dfa9a4304b18da1c0c4dbaa3edb366728501d3","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     gaofei \u003cgao.fei@inspur.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2018-06-13 11:18:13 +0800"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Fix typos"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Change-Id: I6ab47637ef2d2f97f35188a84e741274c2b504e8"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5f7c97a3_2fd227fe","line":7,"updated":"2018-06-13 03:31:07.000000000","message":"The commit message could have more work. According to the change it\u0027s fixing an extra \u0027and\u0027, which I guess could be considered a typo. But it\u0027s only 1. Maybe it should go something like:\n\n Fix typo in sharding docs\n\n This patch removes an additional and added to a sentence.\n\nUsually I\u0027d just push a patch to clean up the commit message, but didn\u0027t know how you\u0027d feel if I did that :)\n\nThe idea is, once the patch lands the commit message is all we really have to identify the patch in the repository, so having something less generic and specifies what the patch does is really useful.","commit_id":"1121702168f2073895364d75907bfc8b4fb73c80"}]}