)]}'
{
  "commit": "12aa0be5d47d8759e27a1ee412b2f95b9906898b",
  "tree": "b34d080e817b9a94809b24734a0bf64ed9c5605c",
  "parents": [
    "12575e5bfe4292067d805404f6c6524f64a3ab86"
  ],
  "author": {
    "name": "Carl-Daniel Hailfinger",
    "email": "c-d.hailfinger.devel.2006@gmx.net",
    "time": "Mon Mar 22 23:47:38 2010 +0000"
  },
  "committer": {
    "name": "Carl-Daniel Hailfinger",
    "email": "c-d.hailfinger.devel.2006@gmx.net",
    "time": "Mon Mar 22 23:47:38 2010 +0000"
  },
  "message": "Check 82802AB probing results for flash contents too\n\nJEDEC ID probing checks the parity of the vendor ID and verifies that\nthe ID differs from the flash chip contents. Add the same feature to\n82802AB ID probing.\n\nThis should reduce the number of lines we have to look at to determine\nif we\u0027re missing a chip definition or if we need a board enable. Just\nuse grep on the log: grep -v \"parity violation\" To narrow it down\nfurther, try: grep -v \"id1 is normal flash content, id2 is normal flash\ncontent\" And of course you want to ignore the skipped probes: grep -v\n\"skipped\" The remaining lines are worth examining, and if those look\nbogus as well, you can bet that we just need a board enable.\n\nCorresponding to flashrom svn r971.\n\nSigned-off-by: Carl-Daniel Hailfinger \u003cc-d.hailfinger.devel.2006@gmx.net\u003e\nAcked-by: Michael Karcher \u003cflashrom@mkarcher.dialup.fu-berlin.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "191114bcfea72840bf3087a45c648b0b248ad75b",
      "old_mode": 33188,
      "old_path": "82802ab.c",
      "new_id": "b6bd689875c72cff2b556111918369cccc7da822",
      "new_mode": 33188,
      "new_path": "82802ab.c"
    }
  ]
}