)]}'
{
  "commit": "5eb7a58c1bc34f64c43f98578ce5b9be21a3f152",
  "tree": "fe01f2dc6954114e565a0a5eaad30b54a29d21db",
  "parents": [
    "7427569e2572cc8182e056876c0c67ddae213fc3"
  ],
  "author": {
    "name": "Nico Huber",
    "email": "nico.h@gmx.de",
    "time": "Tue Nov 05 10:30:19 2024 +0100"
  },
  "committer": {
    "name": "Nico Huber",
    "email": "nico.h@gmx.de",
    "time": "Wed Nov 06 11:15:42 2024 +0000"
  },
  "message": "Drop 1s delay before automatic verification\n\nThis delay was added in commit 8ab49e72af84 (Disallow erase/write for\nknown bad chips so people won\u0027t try without a clear understanding) to\nhelp with \"a few reports where verify directly after erase had unplea-\nsant side effects\".\n\nSince 2011 however,  commit b4061f61cdf9  (Move erase verification to\ngeneric code),  we read each erased block back directly,  without any\ndelay.  So it seems the original problem is either gone, or would hit\nus much earlier.\n\nGrepping through 3 years of mailing-list archives, also didn\u0027t reveal\nanything specific.  Most reports of failed verifications could be ex-\nplained with write protections. More recent ones were about SPI flash\nchips with auto address increment (AAI) writes, where flashrom didn\u0027t\nerase automatically before writing  (and hence gave rather suspicious\nresults).\n\nChange-Id: I9871ee7085156816bfffb117cda60b9267990609\nSigned-off-by: Nico Huber \u003cnico.h@gmx.de\u003e\nReviewed-on: https://review.sourcearcade.org/c/flashprog/+/269\nReviewed-by: Angel Pons \u003cth3fanbus@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0a94c63869ee17e18dab815326385d3654edb599",
      "old_mode": 33188,
      "old_path": "flashprog.c",
      "new_id": "3e143853b5cdec081af87b67bd9ff26e498fcb32",
      "new_mode": 33188,
      "new_path": "flashprog.c"
    }
  ]
}