)]}'
{
  "commit": "ca716364f045da710ddef7fc6420bd6760e45b56",
  "tree": "e29039d09181ff4a234373d2f65342c32b5f5e12",
  "parents": [
    "eb489bb1eceea0d710cd5f5122d37213300ceef6"
  ],
  "author": {
    "name": "Kevin Wolf",
    "email": "kwolf@redhat.com",
    "time": "Thu Nov 10 18:13:59 2011 +0100"
  },
  "committer": {
    "name": "Kevin Wolf",
    "email": "kwolf@redhat.com",
    "time": "Fri Nov 11 14:02:59 2011 +0100"
  },
  "message": "block: Make cache\u003dunsafe flush to the OS\n\ncache\u003dunsafe completely ignored bdrv_flush, because flushing the host disk\ncosts a lot of performance. However, this means that qcow2 images (and\npotentially any other format) can lose data even after the guest has issued a\nflush if the qemu process crashes/is killed. In case of a host crash, data loss\nis certainly expected with cache\u003dunsafe, but if just the qemu process dies this\nis a bit too unsafe.\n\nNow that we have two separate flush functions, we can choose to flush\neverythign to the OS, but don\u0027t enforce that it\u0027s physically written to the\ndisk.\n\nSigned-off-by: Kevin Wolf \u003ckwolf@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b1a462956ff8c9a157b92b898e8746a8edec7454",
      "old_mode": 33188,
      "old_path": "block.c",
      "new_id": "86910b046c27e116adeb0c575a1319dc53dde276",
      "new_mode": 33188,
      "new_path": "block.c"
    }
  ]
}