)]}'
{
  "commit": "2f52e20597ebd55ede668b2b7d162a84f419b03e",
  "tree": "661fd001dfeeab007a71e9469e42dae58f0f298d",
  "parents": [
    "999387782f736d7ac0083f4f02e2bc4ce7a9a27b"
  ],
  "author": {
    "name": "Eric Blake",
    "email": "eblake@redhat.com",
    "time": "Thu Jul 30 16:33:07 2015 -0600"
  },
  "committer": {
    "name": "Markus Armbruster",
    "email": "armbru@redhat.com",
    "time": "Fri Sep 04 15:47:14 2015 +0200"
  },
  "message": "qapi: Document that input visitor semantics are prone to leaks\n\nMost functions that can return a pointer or set an Error ** value\nare decent enough to guarantee a NULL return when reporting an error.\nNot so with our generated qapi visitor functions.  If the caller\nis not careful to clean up partially-allocated objects on error,\nthen the caller suffers a memory leak.\n\nProperly fixing it is probably complex enough to save for a later\nday, so merely document it for now.\n\nSigned-off-by: Eric Blake \u003ceblake@redhat.com\u003e\nMessage-Id: \u003c1438295587-19069-1-git-send-email-eblake@redhat.com\u003e\nSigned-off-by: Markus Armbruster \u003carmbru@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "73f136fc1d512c0aa5c21ffe0008928896961ec3",
      "old_mode": 33188,
      "old_path": "scripts/qapi-visit.py",
      "new_id": "eec5f1f4c5881f6213337146d20d8a7e7a15cbc7",
      "new_mode": 33188,
      "new_path": "scripts/qapi-visit.py"
    },
    {
      "type": "modify",
      "old_id": "b7a87ee35153fec4b15f6601433a9bfc7241be31",
      "old_mode": 33188,
      "old_path": "tests/test-qmp-input-visitor.c",
      "new_id": "a5cfefae8bbce3b79f5e13dc2f80918f6e4450be",
      "new_mode": 33188,
      "new_path": "tests/test-qmp-input-visitor.c"
    }
  ]
}