)]}'
{
  "commit": "c64b16c4bfd471219709ccabc55f090355edd62a",
  "tree": "6a40234b547d786ab42eded33cb66aa8f6f2b4dc",
  "parents": [
    "a8af2c3b643a892c0e4cc8f59efd16209f224228",
    "3ac708cb54daf156bbf8f203a66499cbd5269b50"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Mon Jan 06 21:02:04 2020 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Jan 06 21:02:04 2020 +0000"
  },
  "message": "Merge #128\n\n128: Remove unstable offset_from feature r\u003dtorfmaster a\u003dtorfmaster\n\n# Summary\r\n\r\nIn this PR I remove the unstable `offset_from` feature which is used to calculate the number of bytes of a slice of bytes in a given range of addresses (the flash region). Clearly, the feature provides a safe and concise way of computing this. However, I find that using a minimal number of unstable/experimental features here has a higher value.\n\nCo-authored-by: torfmaster \u003cbriefe@kebes.de\u003e\n",
  "tree_diff": []
}