)]}'
{
  "commit": "b1e36f2872b8f645b806a151e3e88540adcde614",
  "tree": "e3f526ed2b9dbbcd5cb22721858f89c0fea62ab6",
  "parents": [
    "3d5cd513fa47cd100bbc6018be072f247fe717fc"
  ],
  "author": {
    "name": "John Koleszar",
    "email": "jkoleszar@google.com",
    "time": "Thu Jun 24 08:41:51 2010 -0400"
  },
  "committer": {
    "name": "John Koleszar",
    "email": "jkoleszar@google.com",
    "time": "Thu Jun 24 08:41:56 2010 -0400"
  },
  "message": "ivfenc: correct fixed kf interval, --disable-kf\n\nivfenc was setting the VPX_KF_FIXED mode when the kf_min_dist and\nkf_max_dist parameters were set to each other. This flag actually means\nthat keyframes are disabled, and that name was deprecated to avoid\nconfusion such as this. Instead, a new option is exposed for setting the\nVPX_KF_DISABLED mode, and the intervals are passed through to the codec,\nwhich will do automatic placement at a fixed interval as expected.\n\nChange-Id: I15abbec5936f39d5901878b4bc154372fbc23a43\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "11f2a8fefafb31f9b23f4d4ea378b29587ee8f39",
      "old_mode": 33188,
      "old_path": "ivfenc.c",
      "new_id": "3487b3594a43afe73736333209f16ce92d32b152",
      "new_mode": 33188,
      "new_path": "ivfenc.c"
    }
  ]
}