)]}'
{
  "commit": "aaa2f6b460d79157ce271b5a143c19fc4c6aa34e",
  "tree": "aed636c361bf82fb68f7f4376b4b572eb0032bf7",
  "parents": [
    "de1a04029d5bf0ca5d2c82b95569cdbce3a92421"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Oct 17 19:52:16 2017 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Oct 17 19:52:16 2017 +0300"
  },
  "message": "Core: free shared memory zones only after reconfiguration.\n\nThis is what usually happens for zones no longer used in the new\nconfiguration, but zones where size or tag were changed were freed\nwhen creating new memory zones.  If reconfiguration failed (for\nexample, due to a conflicting listening socket), this resulted in a\nsegmentation fault in the master process.\n\nReported by Zhihua Cao,\nhttp://mailman.nginx.org/pipermail/nginx-devel/2017-October/010536.html.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "675a50614ab23fc60ce320600577ad5e54fce440",
      "old_mode": 33188,
      "old_path": "src/core/ngx_cycle.c",
      "new_id": "f3ac24d7a592a86a655d3c62a6d46bba1e3ce20c",
      "new_mode": 33188,
      "new_path": "src/core/ngx_cycle.c"
    }
  ]
}