)]}'
{
  "commit": "7de0be6573afc9dcfb6aa0ded167ad6a8730f727",
  "tree": "aa65a24f5afc2320f95b3aff27bca98480c97024",
  "parents": [
    "a24712af54259dd744a49447658521325f10a721"
  ],
  "author": {
    "name": "Markus Armbruster",
    "email": "armbru@redhat.com",
    "time": "Thu Oct 15 17:08:35 2015 +0200"
  },
  "committer": {
    "name": "Markus Armbruster",
    "email": "armbru@redhat.com",
    "time": "Fri Oct 30 09:05:38 2015 +0100"
  },
  "message": "monitor: Throttle event VSERPORT_CHANGE separately by \"id\"\n\nVSERPORT_CHANGE is emitted when the guest opens or closes a\nvirtio-serial port.  The event\u0027s member \"id\" identifies the port.\n\nWhen several events arrive quickly, throttling drops all but the last\nof them.  Because of that, a QMP client must assume that *any* port\nmay have changed state when it receives a VSERPORT_CHANGE event and\nthrottling may have happened.\n\nMake the event more useful by throttling it for each port separately.\n\nSigned-off-by: Markus Armbruster \u003carmbru@redhat.com\u003e\nReviewed-by: Eric Blake \u003ceblake@redhat.com\u003e\nMessage-Id: \u003c1444921716-9511-7-git-send-email-armbru@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "525d8e486dd8a154f6e037f40dfe5d0edcdfb500",
      "old_mode": 33188,
      "old_path": "monitor.c",
      "new_id": "6cd747f4f96cc77d785f65f93c21be37d7d93890",
      "new_mode": 33188,
      "new_path": "monitor.c"
    }
  ]
}