Overview
| Comment: | docs: the clone records the horizon cursor |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk | feat/horizon-cones |
| Files: | files | file ages | folders |
| SHA3-256: |
22bbf792b349d6c5cc993835061b94d8 |
| User & Date: | [email protected] on 2026-10-22 21:04:14.000 |
| Other Links: | branch diff | manifest | tags |
Context
|
2026-10-22
| ||
| 21:16 |
Merge branch 'wip/merge-renames' into feat/horizon-cones
Merges follow renames as fossil's merge does: its name pivot, find_filename_changes and file matching ported, so a file renamed on one side and edited on the other merges into the renamed file. Matches fossil 2.28 on 13 rename scenarios. Repo.Merge no longer brings back files the merge deleted. check-in: 4bccd3f803 user: [email protected] tags: feat/horizon-cones, trunk | |
| 21:04 | docs: the clone records the horizon cursor check-in: 22bbf792b3 user: [email protected] tags: feat/horizon-cones, trunk | |
| 21:04 |
conform(horizon): the cursor rows are covered
HZ-6.2-11: every reply to a request the origin classified carries the cursor; the operation-less round after a clone's last page answers no pull or clone card, so it is not a classified request, as in zit. HZ-6.2-12: a client records and sends the cursor whenever its transport names the origin; without one it announces in full, which the advisory cursor of §6.2.6 allows. check-in: a33cbbf951 user: [email protected] tags: feat/horizon-cones, trunk | |
Changes
Modified CHANGELOG.md
from [dd5050b652]
to [b4c9e12ae2].
[diff]
Modified docs/site/content/docs/sparse-and-horizons.md
from [d2a1fea1fe]
to [1d6603f41c].
[diff]