)]}'
{
  "commit": "7f9305501c6b10a257a9cadc3db7cab5427e6145",
  "tree": "7c861392abbe103eaa06ed8c1a8a4a14df02000a",
  "parents": [
    "ab322593a6c6ceda6b5d1a93a9aa9eef4dcd9cc6",
    "de3314a497a5b86270d7742a59506646d301a028",
    "d11dc52201faf2d363036d5d1afe8fca3d40f2a0"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Fri Feb 12 18:41:42 2021 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Feb 12 18:41:42 2021 +0000"
  },
  "message": "Merge #275 #276\n\n275: Add `libtock_runtime` startup code. r\u003dalistair23 a\u003djrvanwhy\n\nThis includes:\r\n\r\n1. `rust_start`: The first Rust code to run in a process\r\n1. `set_main!`: Used to specify `main` in a process binary\r\n1. `stack_size!`: Used to specify the stack size in a process binary\r\n1. Documentation of the startup sequence, including the 3 above steps.\r\n\r\nThe documentation refers to a two things that haven\u0027t been implemented yet:\r\n1. Debug syscalls performed by `rust_start` -- unimplemented because `memop` is\r\n   still unimplemented.\r\n1. The `exit` system call.\n\n276: Add a tock2 submodule with a tock-2.0-dev kernel. r\u003dalistair23 a\u003djrvanwhy\n\nI intend to use this kernel in integration tests for the Tock 2.0 crates. When we are ready to remove Tock 1.x support, I will remove the duplicate submodule.\n\nCo-authored-by: Johnathan Van Why \u003cjrvanwhy@google.com\u003e\n",
  "tree_diff": []
}