Skip to content
go-libfossil Check-in [ed53ee9c59]
Login

Check-in [ed53ee9c59]

Overview
Comment:Merge branch 'wip/clone-perf' into feat/horizon-cones
Timelines: family | ancestors | descendants | both | trunk | feat/horizon-cones
Files: files | file ages | folders
SHA3-256: ed53ee9c598e6be7461b8a3a33c0e8da9a5557a82a85772157a02e5c3e702e20
User & Date: [email protected] on 2026-10-23 15:19:13.000
Other Links: branch diff | manifest | tags
Context
2026-10-23
15:19
docs(changelog): sparse clones of large repositories, late cherrypick sources leaf check-in: ae7b0cee31 user: [email protected] tags: feat/horizon-cones, trunk
15:19
Merge branch 'wip/clone-perf' into feat/horizon-cones check-in: ed53ee9c59 user: [email protected] tags: feat/horizon-cones, trunk
15:11
fix(manifest): keep a pull's file waits; skip them only in a sparse clone

The previous change let a sparse store link a check-in before its files. A pull that deepens a structural horizon then linked the new base first and left its files unrequested phantoms, and the merge over it found no content (TestRepoMergeDeepensAcrossHorizon).

A pull waits on a check-in's files again, except those the store cone's path members exclude, which never arrive. Only a clone into a sparse store waits on none: the origin's walk sends every file the store keeps in the same session, and nothing reads the store before the clone ends. check-in: 35566881ec user: [email protected] tags: feat/horizon-cones, trunk

03:28
Merge branch 'wip/hz-close-sync' into feat/horizon-cones

An origin answering a horizon request never sends a cluster, even one a gimme names; an origin may name a history URL in horizon-served (horizon-history-url), which the client reports; and a merge with no peer to ask refuses whenever either side's ancestry crosses the horizon. Conflicts in the changelog and the CLI horizon tests kept both sides. check-in: c4b191ed05 user: [email protected] tags: feat/horizon-cones, trunk

Changes