)]}'
{
  "commit": "01fb2705bd19a6e9c1207446793064dbd141df5f",
  "tree": "5fdb13f3e19f7d52bef064098ea7cd76d6481453",
  "parents": [
    "d40593dd9033d39a5e4cc32915c5eb28f3e858b6"
  ],
  "author": {
    "name": "Kevin Wolf",
    "email": "kwolf@redhat.com",
    "time": "Mon Jul 07 17:00:37 2014 +0200"
  },
  "committer": {
    "name": "Kevin Wolf",
    "email": "kwolf@redhat.com",
    "time": "Wed Jul 09 15:50:11 2014 +0200"
  },
  "message": "block: Fix bdrv_is_allocated() return value\n\nbdrv_is_allocated() should return either 0 or 1 in successful cases.\nWe\u0027re lucky that currently, the callers that rely on this (e.g. because\nthey check for ret \u003d\u003d 1) don\u0027t seem to break badly. They just might skip\nsome optimisation or in the case of qemu-io \u0027map\u0027 print separate lines\nwhere a single line would suffice. In theory, a wrong allocation status\ncould lead to image corruption with certain operations, so let\u0027s fix\nthis quickly.\n\nSigned-off-by: Kevin Wolf \u003ckwolf@redhat.com\u003e\nReviewed-by: Eric Blake \u003ceblake@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8800a6b5b37215f8c264676dce5857e2d206a8b4",
      "old_mode": 33188,
      "old_path": "block.c",
      "new_id": "c9629a44b99c8adf0de3c58e879c73118e8559f8",
      "new_mode": 33188,
      "new_path": "block.c"
    }
  ]
}