)]}'
{
  "commit": "5abbf0ee4d87c695deb1c3fca9bb994b93a3e3be",
  "tree": "f4c1067304268d1d1d7e823b97e8d8ec0bcb2462",
  "parents": [
    "247147fbc107f818630c4044931de39b89c99342"
  ],
  "author": {
    "name": "Kevin Wolf",
    "email": "kwolf@redhat.com",
    "time": "Thu Sep 18 11:48:34 2014 +0200"
  },
  "committer": {
    "name": "Kevin Wolf",
    "email": "kwolf@redhat.com",
    "time": "Thu Sep 25 15:24:14 2014 +0200"
  },
  "message": "block: Catch simultaneous usage of options and their aliases\n\nWhile thinking about precedence of conflicting block device options from\ndifferent sources, I noticed that you can specify both an option and its\nlegacy alias at the same time (e.g. readonly\u003don,read-only\u003doff). Rather\nthan specifying the order of precedence, we should simply forbid such\ncombinations.\n\nSigned-off-by: Kevin Wolf \u003ckwolf@redhat.com\u003e\nReviewed-by: Benoît Canet \u003cbenoit.canet@nodalink.com\u003e\nReviewed-by: Markus Armbruster \u003carmbru@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "88f79282e920d8344a4117f7b8644d56c5b6d6ff",
      "old_mode": 33188,
      "old_path": "blockdev.c",
      "new_id": "ad436488b7f08b178af192cd89aadfec931d37d3",
      "new_mode": 33188,
      "new_path": "blockdev.c"
    },
    {
      "type": "modify",
      "old_id": "a41334e022aff6b9dc8a6e09358cc6f055681c99",
      "old_mode": 33261,
      "old_path": "tests/qemu-iotests/051",
      "new_id": "11c858f27dab1169187b4b1da6b3eaf32c44d709",
      "new_mode": 33261,
      "new_path": "tests/qemu-iotests/051"
    },
    {
      "type": "modify",
      "old_id": "a3f28209c8b22cf0cfda502532fedcb86e3fb0fd",
      "old_mode": 33188,
      "old_path": "tests/qemu-iotests/051.out",
      "new_id": "2c7e8087655614bdad67840154641a265e1f2ea2",
      "new_mode": 33188,
      "new_path": "tests/qemu-iotests/051.out"
    }
  ]
}