)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6198,"name":"Peter Portante","email":"peter.a.portante@gmail.com","username":"peter-a-portante"},"change_message_id":"7adfbf391bd1fb873e3c7c25377585749722da41","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Alex Gaynor \u003calex.gaynor@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2014-05-19 07:21:03 -0700"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Converted several files to have Python3 friendly syntax"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Change-Id: Id3fcbab390f08dcb3380cfda16d7b820b03ef683"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"7adec928_60f06dc9","line":7,"updated":"2014-05-19 14:46:35.000000000","message":"So this is really just about using the print function, right?\n\nIs there a hacking thing that can be turned on with this change to prevent them being added back in future commits?","commit_id":"3f80fc5cba79f101cb5cd931cbd1db4a0aa99283"},{"author":{"_account_id":7680,"name":"Alex Gaynor","email":"alex.gaynor@gmail.com","username":"alex_gaynor"},"change_message_id":"236fe7851d4ac3b18ccf2d0ba5fe85a3eb79b2e5","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Alex Gaynor \u003calex.gaynor@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2014-05-19 07:21:03 -0700"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Converted several files to have Python3 friendly syntax"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Change-Id: Id3fcbab390f08dcb3380cfda16d7b820b03ef683"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1ae5cdf2_e99ac912","line":7,"in_reply_to":"1ae5cdf2_18467d4f","updated":"2014-06-12 18:20:16.000000000","message":"Done","commit_id":"3f80fc5cba79f101cb5cd931cbd1db4a0aa99283"},{"author":{"_account_id":7233,"name":"Matthew Oliver","email":"matt@oliver.net.au","username":"mattoliverau"},"change_message_id":"2e7e885a5d2e7abdb8253ddb8374ef9194bed6da","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Alex Gaynor \u003calex.gaynor@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2014-05-19 07:21:03 -0700"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Converted several files to have Python3 friendly syntax"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Change-Id: Id3fcbab390f08dcb3380cfda16d7b820b03ef683"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1ae5cdf2_18467d4f","line":7,"in_reply_to":"7adec928_60f06dc9","updated":"2014-06-04 08:04:20.000000000","message":"It does just seem to be the print function, which is great BTW. But can this be added to the commit message to make it more meaningful? \n\nSomething like:\n \n  Changed several files to be Python3 friendly\n\n  The print syntax has been changed to be Python3 compatible.\n\nNOTE: that openstack has recommended structure where the first line is limited to 50 characters: \nhttps://wiki.openstack.org/wiki/GitCommitMessages#Summary_of_GIT_commit_message_structure","commit_id":"3f80fc5cba79f101cb5cd931cbd1db4a0aa99283"}]}