)]}'
{
  "commit": "24b432ea918d096f79ddc84e382a66934d578934",
  "tree": "488031e30f95a87fcd6514823ae2e945536424ff",
  "parents": [
    "4a213a7d6bb6b96edb27f6f1e5b9c522385d3350"
  ],
  "author": {
    "name": "Johnathan Van Why",
    "email": "jrvanwhy@google.com",
    "time": "Thu Apr 01 14:20:46 2021 -0700"
  },
  "committer": {
    "name": "Johnathan Van Why",
    "email": "jrvanwhy@google.com",
    "time": "Thu Apr 01 14:20:46 2021 -0700"
  },
  "message": "Typo fix (from code review suggestion), plus change `libtock` to support pluggable panic handler and optional dynamic memory allocation.\n\nI was under the impression that using cargo features was making our CI slow. That impression is incorrect -- cargo caches build artifacts with different feature combinations perfectly fine. We can use feature flags to allow `libtock` to support pluggable panic handlers and optional memory allocation.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0c6952bf2b113c5af0d432b2aeb1638286e3e0e1",
      "old_mode": 33188,
      "old_path": "doc/Overview.md",
      "new_id": "c3145aebf2ed28d15e6bcc2809bc207d6c595adc",
      "new_mode": 33188,
      "new_path": "doc/Overview.md"
    }
  ]
}