)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":679,"name":"Kevin L. Mitchell","email":"klmitch@mit.edu","username":"klmitch"},"change_message_id":"fb0d12069eda35c3ff8046bb53c883326382dce8","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Attach and Detach iSCSI volume"},{"line_number":12,"context_line":"Get volume connector"},{"line_number":13,"context_line":"Glance change to fix image download to ESX"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Change-Id: I25e0c79ffb0b762726fb931233f7beeb53092a34"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"AAAAM3%2F%2Fbpk%3D","line":13,"updated":"2013-01-22 19:29:00.000000000","message":"This isn\u0027t exactly what I had in mind.  The body of the commit message should have a detailed description of the patch, detailed enough \"that one does not have to refer to external resources to determine its high-level functionality.\" This last is quoted from HACKING.rst; I would suggest you read the section on commit messages in there, as well as the page at http://wiki.openstack.org/GitCommitMessages\n\nAs it stands, I consider this commit message to be barely acceptable, but I\u0027m not convinced that other reviewers will.  I would strongly encourage you to revise the commit message to be more detailed.","commit_id":"fd7701f001ee27165c234afd7979ae98ebd9b1ea"}]}
