Pat Pannuto
Pat Pannuto
Updated. Now with 100% fewer controversial `@` changes.
@alevy Why did this need a rebase? It should have merged cleanly, no? The last commit ( https://github.com/tock/libtock-c/pull/470/commits/54b93c4018dfca66ed80efff4306d54bf4d6e5c1 ) needs to update to point to 2e6baf26e9d8cd4f819baf1b0fab4e9c5e3e742e now...
I do think the new github UX is confusing, but I think the "out of date" is just a warning that clicking Merge will create a merge commit [while rebase...
Undid the rebase with force push from my laptop still at old head. Should be good to go.
https://github.com/tock/libtock-c/pull/476
Hmm.. I'm of two minds on the cmake issue. I do think there is probably some utility in an example that shows how one could integrate libtock with an external...
#470 is my best solution to this — hopefully that is sufficient as-is. If not, we can make updates there?
Closing in favor of #470.
While I see your point re preserving existing behavior, my instinct is that preserving specialty spaces in the input string would actually be the better default behavior — if source...
Here's what things look like if you expand `H` to `HashKind` and `S` to `SignatureKind` as well: https://github.com/tock/tock/compare/write-out-crypto-types-too?expand=1 I do favor that, though I cede the point that it is...