)]}'
{
  "commit": "f1b5286803ee66f73034f1f5e0e1cf14f4415f94",
  "tree": "9a47d0fc8e4ffbe91edc1e32ad5532e4fffa12c7",
  "parents": [
    "bc6694d43a68baa864dba7742354a379a3347f33"
  ],
  "author": {
    "name": "Kevin Wolf",
    "email": "kwolf@redhat.com",
    "time": "Wed Jan 27 13:12:35 2010 +0100"
  },
  "committer": {
    "name": "Anthony Liguori",
    "email": "aliguori@us.ibm.com",
    "time": "Fri Jan 29 09:53:01 2010 -0600"
  },
  "message": "virtio-blk: Fix restart after read error\n\nCurrent code assumes that only write requests are ever going to be restarted.\nThis is wrong since rerror\u003dstop exists. Instead of directly starting writes,\nuse the same request processing as used for new requests.\n\nSigned-off-by: Kevin Wolf \u003ckwolf@redhat.com\u003e\nSigned-off-by: Anthony Liguori \u003caliguori@us.ibm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "82f96e52aff444ae1973e6a0ec63737908217b68",
      "old_mode": 33188,
      "old_path": "hw/virtio-blk.c",
      "new_id": "5a413b94297d5991657e0ac1fa72c242c358bd65",
      "new_mode": 33188,
      "new_path": "hw/virtio-blk.c"
    }
  ]
}
