| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Two "X" in the same section, unrelated, can be more confusing than clarifying.
|
|
|
|
|
|
| |
- more than two perspectives
- avoid "deployment" to refer to "log operations"
- don't say "idiot"
|
|
|
|
| |
So let's wait with using it. The sentence stands fine without it.
|
|
|
|
|
|
|
|
| |
They're also not typically communicated in a repository of any kind.
BGP updates _could_ of course be logged for non-realtime historical
storage (archiving) but as an example this early in the text it's
mostly confusing.
|
|
|
|
|
|
|
|
|
| |
- Improved introduction so that it gives a better intuition of how we
think about sigsum logging and what our contribution actually is
- Clarified that monitoring is a 4th step (monkey-patched)
- Added checkpoint as part of our design description
- Emphasized witnessing at the start of 'how it works'
- A bunch of minor edits and clarifications
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|