)]}'
{
  "commit": "a58f6e9b547fd1930a673c526db4476f2ccfaa77",
  "tree": "e5023db15f8d89dd681843c8b2e195476445f5c2",
  "parents": [
    "f20b7beff054eb316088d590094d9efbc68dbee1"
  ],
  "author": {
    "name": "Stefan Tauner",
    "email": "stefan.tauner@alumni.tuwien.ac.at",
    "time": "Sat May 10 09:25:44 2014 +0000"
  },
  "committer": {
    "name": "Stefan Tauner",
    "email": "stefan.tauner@alumni.tuwien.ac.at",
    "time": "Sat May 10 09:25:44 2014 +0000"
  },
  "message": "Refine messages related to erase/write recovery\n\nWe are more verbose inside erase_and_write_flash() although it does not\nmatter as much as at the end of the whole process in doit().\n\nNew output for the non-fatal (i.e. read-protected + successful recovery read) case:\n\nReading old flash chip contents... done.\nErasing and writing flash chip... spi_block_erase_d8 failed during command execution at address 0x8000\nReading current flash chip contents... done. spi_chip_erase_c7 failed during command execution\nFAILED!\nUh oh. Erase/write failed. Checking if anything has changed.\nReading current flash chip contents... done.\nGood, writing to the flash chip apparently didn\u0027t do anything.\nPlease check the connections (especially those to write protection pins) between\nthe programmer and the flash chip. If you think the error is caused by flashrom\nplease report this on IRC at chat.freenode.net (channel #flashrom) or\nmail flashrom@flashrom.org, thanks!\n\nCorresponding to flashrom svn r1790.\n\nSigned-off-by: Stefan Tauner \u003cstefan.tauner@alumni.tuwien.ac.at\u003e\nAcked-by: Stefan Tauner \u003cstefan.tauner@alumni.tuwien.ac.at\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9e87164da5bc25e7cfad75165acddf5b55fe408d",
      "old_mode": 33188,
      "old_path": "flashrom.c",
      "new_id": "b3661c13ddca0557d4a4ddfd37ecae4e228f2451",
      "new_mode": 33188,
      "new_path": "flashrom.c"
    }
  ]
}