summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Bracht Laumann Jespersen <t@laumann.xyz>2022-09-05 13:29:52 +0200
committerThomas Bracht Laumann Jespersen <t@laumann.xyz>2022-09-05 13:29:52 +0200
commit7c6f1c4ffa125b9e07f30b25fa82ef2ede32cfb6 (patch)
tree757ff0dea1b0b8d5f482637cb2572e79fdefdc1a
parentb76156664e8361a5ac8a3bf1d88900d46afc7821 (diff)
ani/log; minor style changes
-rw-r--r--site/ani/2022-08-20-log.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/site/ani/2022-08-20-log.md b/site/ani/2022-08-20-log.md
index a66e273..585803a 100644
--- a/site/ani/2022-08-20-log.md
+++ b/site/ani/2022-08-20-log.md
@@ -10,7 +10,7 @@ subfolders: "change" and "pristine".
* "change" appears to be organized much like Git's "objects" folder in that the
changes are referenced by a hash. A hash like
U6TQX5Z2NF6GX3SRLUBQGCZ7WAXNYMWWZ2YMADUSG4EWVKNV2BIAC is stored in the file:
- `.pijul/change/U6/TQX5Z2NF6GX3SRLUBQGCZ7WAXNYMWWZ2YMADUSG4EWVKNV2BIAC`.
+ `.pijul/change/U6/TQX5Z2NF6GX3SRLUBQGCZ7WAXNYMWWZ2YMADUSG4EWVKNV2BIAC.change`.
* "pristine" contains only... a "db" file?
We'll forget about the "pristine" folder for now and get back to that later. In
@@ -20,6 +20,7 @@ this write-up we'll focus on the structure of change files.
The overall format of a `.change` file is something like this:
+<pre style="border: none"><code>
┌────────────────┐
│ offsets │ fixed 56 bytes
├┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┤
@@ -29,6 +30,7 @@ The overall format of a `.change` file is something like this:
├┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┤
│ contents │ = zstd_compress(contents)
└────────────────┘
+</code></pre>
The first part contains information about offsets into the rest of the file. The
remaining three segments: hashed, unhashed, and contents are all compressed with