)]}'
{
  "commit": "e2982c3a27ab4c0879e61de3c9c57b838f7d0966",
  "tree": "6d01634e3bf1c3e6b3eabe838f90d5e31173071e",
  "parents": [
    "eb863add0204210480d018a3298ca22e4eadf3ce"
  ],
  "author": {
    "name": "Michael Tokarev",
    "email": "mjt@tls.msk.ru",
    "time": "Wed Mar 30 16:31:05 2011 +0400"
  },
  "committer": {
    "name": "Kevin Wolf",
    "email": "kwolf@redhat.com",
    "time": "Thu Apr 07 13:51:48 2011 +0200"
  },
  "message": "exit if -drive specified is invalid instead of ignoring the \"wrong\" -drive\n\nThis fixes the problem when qemu continues even if -drive specification\nis somehow invalid, resulting in a mess.  Applicable for both current\nmaster and for stable-0.14 (and the same issue exist 0.13 and 0.12 too).\n\nThe prob can actually be seriuos: when you start guest with two drives\nand make an error in the specification of one of them, and the guest\nhas something like a raid array on the two drives, guest may start failing\nthat array or kick \"missing\" drives which may result in a mess - this is\nwhat actually happened to me, I did\u0027t want a resync at all, and a resync\nresulted in re-writing (and allocating) a 4TB virtual drive I used for\ntesting, which in turn resulted in my filesystem filling up and whole\nthing failing badly.  Yes it was just testing VM, I experimented with\nlarger raid arrays, but the end result was quite, well, unexpected.\n\nSigned-off-by: Michael Tokarev \u003cmjt@tls.msk.ru\u003e\nAcked-by: Jes Sorensen \u003cJes.Sorensen@redhat.com\u003e\nSigned-off-by: Kevin Wolf \u003ckwolf@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "de232b75e6981931c316aec74970e1725c636346",
      "old_mode": 33188,
      "old_path": "vl.c",
      "new_id": "68c3b532bce593cd1f4f452fd1b3077a6c2f2cb9",
      "new_mode": 33188,
      "new_path": "vl.c"
    }
  ]
}