)]}'
{
  "commit": "a8707c08f4f718bb0ed65499d3f43201f6e41455",
  "tree": "8fc3ea9ea924ebc4f28012c11f3c1e70ad60bcb2",
  "parents": [
    "7b0bb5368a7195606eca475d9f4e291ab7227052"
  ],
  "author": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Tue May 18 09:28:43 2010 +1000"
  },
  "committer": {
    "name": "NeilBrown",
    "email": "neilb@suse.de",
    "time": "Tue May 18 15:28:01 2010 +1000"
  },
  "message": "md: simplify updating of event count to sometimes avoid updating spares.\n\nWhen updating the event count for a simple clean \u003c-\u003e dirty transition,\nwe try to avoid updating the spares so they can safely spin-down.\nAs the event_counts across an array must be +/- 1, this means\ndecrementing the event_count on a dirty-\u003eclean transition.\nThis is not always safe and we have to avoid the unsafe time.\nWe current do this with a misguided idea about it being safe or\nnot depending on whether the event_count is odd or even.  This\napproach only works reliably in a few common instances, but easily\nfalls down.\n\nSo instead, simply keep internal state concerning whether it is safe\nor not, and always assume it is not safe when an array is first\nassembled.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fec4abcb9bb4d443e086af8198e9b26de865ee81",
      "old_mode": 33188,
      "old_path": "drivers/md/md.c",
      "new_id": "9ef21d9b8e27394e40c35454ecfea6c75997c443",
      "new_mode": 33188,
      "new_path": "drivers/md/md.c"
    },
    {
      "type": "modify",
      "old_id": "a536f54580970cb1114ed4b4b8717c7381a80d52",
      "old_mode": 33188,
      "old_path": "drivers/md/md.h",
      "new_id": "7ab5ea155452c5b745041e05c155df0ded2dd2c4",
      "new_mode": 33188,
      "new_path": "drivers/md/md.h"
    }
  ]
}