1. 40327a6 Add the "Platform Design Story", which explains the design of `libtock_platform` by demonstrating how to write an efficient `console` driver. by Johnathan Van Why · 4 years, 2 months ago
  2. 6b11969 Weaken my statement about needing a dependency injection mechanism a bit: an alternative mechanism for testing `libtock_core`'s system call error handling logic would be fine as well. by Johnathan Van Why · 4 years, 2 months ago
  3. 920d028 Typo correction: "they code" -> "the code". by Johnathan Van Why · 4 years, 3 months ago
  4. 3d09b3e Document several factors constraining `libtock_core`'s design. by Johnathan Van Why · 4 years, 3 months ago
  5. ac83d58 Mention the Code Review document in CONTRIBUTING, and add some clarifications to the code review document. by Johnathan Van Why · 4 years, 6 months ago
  6. 3a786cb Add a code review policy that clarifies: by Johnathan Van Why · 4 years, 6 months ago
  7. a6c5c9d Switch all crate names to use underscores rather than hyphens. by Johnathan Van Why · 4 years, 7 months ago
  8. 5ca142c Elaborate on the meaning of dependency. by Johnathan Van Why · 4 years, 7 months ago
  9. e861d12 Dependency policy: add a note that the dependencies discussed are for building apps, and expand the "libcore" bullet to the entire toolchain. by Johnathan Van Why · 4 years, 7 months ago
  10. eb33118 Add documentation describing `libtock-rs`'s unaudited third-party dependencies, as required by Tock's threat model. by Johnathan Van Why · 4 years, 7 months ago
  11. 6695e0d docs: Remove outdated README by Alistair Francis · 4 years, 10 months ago
  12. 3620f07 Correct name of RISC-V target by Laura Abbott · 5 years ago
  13. efd0aa9 Review comments by Woyten · 5 years ago