)]}'
{
  "commit": "b8dcf10974e893270e8dd7e5ed5b18536e36f84b",
  "tree": "3ed58c6724289b5fdb9b773ab9aa96f84c719346",
  "parents": [
    "d04c1392c0b5bdd517a7032b158a689b5ab3d79e"
  ],
  "author": {
    "name": "Christopher Haster",
    "email": "chaster@utexas.edu",
    "time": "Sat Nov 28 22:46:11 2020 -0600"
  },
  "committer": {
    "name": "Christopher Haster",
    "email": "chaster@utexas.edu",
    "time": "Sat Nov 28 22:46:11 2020 -0600"
  },
  "message": "Changed lfs_dir_alloc to maximize block cycles for new metadata pairs\n\nPreviously we only bumped the revision count if an eviction would occur\nimmediately (and possibly corrupt littlefs). This works, but does risk\nan unoptimal superblock size if an almost-exhausted superblock was\nallocated during lfs_format.\n\nAs pointed out by tim-nordell-nimbelink, we can align the revision count\nto maximize the number of block cycles without breaking the existing\nrequirements of increasing revision counts.\n\nAs an added benefit, littlefs\u0027s wear-leveling should behave more\nconsistently after this change.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3899c28171d54f17021e63e3208b3bb71f3c9ca7",
      "old_mode": 33188,
      "old_path": "lfs.c",
      "new_id": "ee47fb43a6f79ed838b10fd86e70eaf9f24e674e",
      "new_mode": 33188,
      "new_path": "lfs.c"
    }
  ]
}