Artifact Description [d994a1b615]

Artifact d994a1b61569912354ffce566fcbfc9118f9ac7c1f4c31d6d28ebd68d1bc9889:

• File internal/sync/config_groups.go
  • 2026-10-17 20:57:59 — part of check-in [707ffd05a2] on branch feat/submanifest-reader — feat(sync): carry sub-manifest trees safely (draft-fossil-submanifests-00)

    Gate, announce and configure sub-manifest transfer the way zit does, so the two implementations interoperate and no fossil release is handed a tree it cannot read.

    - 7.2 gate: once the repository has stored an S-bearing artifact, a tree manifest or sub-manifest is withheld from a peer announcing a release below 2.29.0, zit's threshold, with one explicit error card per reply and never by omission. The server applies it to gimme answers and clone batches; the client to gimmes on push, recording each withheld artifact in the result. - This library reads trees, so it announces 22900 in client-version and server-version; a peer holding trees refuses them to anything lower. No fossil release gates any behaviour between 22800 and 22900. - A ci-lock reply carries pragma avoid-submanifests, where avoid-delta-manifests goes, while enable-submanifests is off. - 6.3: the three settings are /project members on the server, which also answers zit's reqconfig /config with them. Clone asks for them as zit's clone does, once, in its cleanup round with zit's scalar marker; fossil answers that with nothing. A reply's settings are staged and applied all or none.

    The examined-blob table's old revision is dropped only when present, so a sweep pays no extra write. (user: [email protected], size: 11425) [annotate] [blame] [check-ins using]

  • 2026-10-21 21:20:46 — part of check-in [7244496a09] on branch main — Merge pull request #437 from danmestas/feat/submanifest-reader

    feat: sub-manifest trees and sparse cones (draft-fossil-submanifests-00, draft-fossil-sparse-cone-00) (user: [email protected], size: 11425) [annotate] [blame] [check-ins using]