)]}'
{
  "commit": "8ab49e72af8465d4527de2ec37b22cd44f7a1169",
  "tree": "5533977c6923fc5ff5e1026383097b584f393ffc",
  "parents": [
    "3426ef6ab8dc13a0f1c306ab5d63e27664fb3e5c"
  ],
  "author": {
    "name": "Carl-Daniel Hailfinger",
    "email": "c-d.hailfinger.devel.2006@gmx.net",
    "time": "Wed Aug 19 13:55:34 2009 +0000"
  },
  "committer": {
    "name": "Carl-Daniel Hailfinger",
    "email": "c-d.hailfinger.devel.2006@gmx.net",
    "time": "Wed Aug 19 13:55:34 2009 +0000"
  },
  "message": "Disallow erase/write for known bad chips so people won\u0027t try without a clear understanding\n\nAllow override with --force.\n\nIf write/erase failed, warn the user to get help and not shutdown/reboot\nthe computer.\n\nWarn that the result of a forced read is often garbage. Too many users\nbelieved that a forced read meant that everything was fine.\n\nWait 1 second between erase and verify. This fixes a few reports where\nverify directly after erase had unpleasant side effects like corrupting\nflash or at least getting incorrect verify results.\n\nCorresponding to flashrom svn r692.\n\nSigned-off-by: Carl-Daniel Hailfinger \u003cc-d.hailfinger.devel.2006@gmx.net\u003e\nAcked-by: Stefan Reinauer \u003cstepan@coresystems.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fb45bd0bffa6bf3f6b35cbc6ffb8ac2edb0b9446",
      "old_mode": 33188,
      "old_path": "flashrom.c",
      "new_id": "b1f947105d141ea6706374829fe05e7cae1f123c",
      "new_mode": 33188,
      "new_path": "flashrom.c"
    }
  ]
}