)]}'
{
  "commit": "04c0dd5c385e04e6d61de8c2e4b42e6a6e670109",
  "tree": "bbc578b95811415e5bf7cc6a7ab772882df50928",
  "parents": [
    "b687f0a01c8705c8c01ff35f521463c4513545be",
    "24b432ea918d096f79ddc84e382a66934d578934"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Thu Apr 08 04:07:48 2021 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Apr 08 04:07:48 2021 +0000"
  },
  "message": "Merge #283\n\n283: [RFC] `libtock-rs` crate organization r\u003dhudson-ayers a\u003djrvanwhy\n\n[Rendered](https://github.com/jrvanwhy/libtock-rs/blob/overview/doc/Overview.md)\r\n\r\nOverview gives a high-level view of the crates in the Tock 2.0 `libtock-rs`. It is intended to be a useful resource for newcomers to this repository.\r\n\r\nAll of the crates mentioned in this document exist at https://github.com/jrvanwhy/libtock-rs/tree/wip, and I am in the process of cleaning them up (adding tests + docs) and sending PRs to merge them here. I developed these crates in my fork because of a chicken-and-egg problem: all of these crates depend on [the rewritten `RawSyscalls`](https://github.com/tock/libtock-rs/pull/282), but I couldn\u0027t be sure my `RawSyscalls` design was correct until these crates were working.\n\nCo-authored-by: Johnathan Van Why \u003cjrvanwhy@google.com\u003e\n",
  "tree_diff": []
}