The artifact hash prefix 2559 is ambiguous and might mean any of the following:
25594861e9dd4465ce5783809869153026d02644a68a08e9c5fd9669530ec06b -
- File src/git/git_import_test.zig — part of check-in [49c08bb191] at 2026-08-13 13:08:34 on branch sub-manifest — git: gather every interop root into src/git/ — cli.zig joins the zit module (nine importers rerouted), moved roots take parent deps through the module; ~986 duplicate test executions eliminated (user: dmestas, size: 152381) [annotate] [blame] [check-ins using] [more...]
2559e637674d2f21728827444de140a3c73789e749536aaec0d27c984e56abb2 -
- File
src/rfc_vectors.zig
— part of check-in
[32ef56aaf4]
at
2026-08-25 21:09:31
on branch rfc-vector-guard
— rfc vectors: keep them inert on disk
An unguarded vector parses as a real artifact, so Fossil crosslinks it into every clone -- two check-ins, a technote, twelve sub-manifest slices and a phantom pair that sync chases forever. Each vector now carries a leading # block; rfc_vectors.zig strips it at comptime so callers still see the exact RFC bytes.
Background and the cleanup that follows: see wiki page 'rfc-vector-ledger'. (user: dmestas, size: 6680) [annotate] [blame] [check-ins using] [more...]
- File
src/rfc_vectors.zig
— part of check-in
[32ef56aaf4]
at
2026-08-25 21:09:31
on branch rfc-vector-guard
— rfc vectors: keep them inert on disk