)]}'
{
  "commit": "d28d737fb9b1f6c2a58821f8a4640adecf99249b",
  "tree": "c26d34c22fd51a49b7b26758a59549a033f2e050",
  "parents": [
    "e4937694b66d1468aec3cd95e90888f291c3f599"
  ],
  "author": {
    "name": "Markus Armbruster",
    "email": "armbru@redhat.com",
    "time": "Fri Dec 18 16:35:21 2015 +0100"
  },
  "committer": {
    "name": "Markus Armbruster",
    "email": "armbru@redhat.com",
    "time": "Wed Jan 13 15:16:18 2016 +0100"
  },
  "message": "vmdk: Clean up \"Invalid extent lines\" error message\n\nvmdk_parse_extents() reports parse errors like this:\n\n    error_setg(errp, \"Invalid extent lines:\\n%s\", p);\n\nwhere p points to the beginning of the malformed line in the image\ndescriptor.  This results in a multi-line error message\n\n    Invalid extent lines:\n    \u003cfirst line that doesn\u0027t parse\u003e\n    \u003cremaining text that may or may not parse, if any\u003e\n\nError messages should not have newlines embedded.  Since the remaining\ntext is not helpful, we can simply report:\n\n    Invalid extent line: \u003cfirst line that doesn\u0027t parse\u003e\n\nCc: Fam Zheng \u003cfamz@redhat.com\u003e\nSigned-off-by: Markus Armbruster \u003carmbru@redhat.com\u003e\nReviewed-by: Eric Blake \u003ceblake@redhat.com\u003e\nMessage-Id: \u003c1450452927-8346-19-git-send-email-armbru@redhat.com\u003e\nReviewed-by: Fam Zheng \u003cfamz@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "08fa3f3b123e435a4ea5a77cfcbd90a3f5ed65dd",
      "old_mode": 33188,
      "old_path": "block/vmdk.c",
      "new_id": "2b5cb00ef1ad4977bcddad5f7ccff5cd099a092e",
      "new_mode": 33188,
      "new_path": "block/vmdk.c"
    },
    {
      "type": "modify",
      "old_id": "d28df5bb622954e4a4a147bd82fed6e565ee046b",
      "old_mode": 33188,
      "old_path": "tests/qemu-iotests/059.out",
      "new_id": "9d506cb80c53cf67edab99b034de0e0afcde5b50",
      "new_mode": 33188,
      "new_path": "tests/qemu-iotests/059.out"
    }
  ]
}