Skip to content
zit Check-in [5fce7e867d]
Login

Check-in [5fce7e867d]

Overview
Comment:zit git export/status: a remembered Git mirror with autopush

git export exports into MIRROR and remembers it, with an autopush URL, push branch and email domain, in repository config; a bare re-run does the round trip. Authors' addresses come from their user-table contact, set with the new users contact. Autopush URLs carrying a password are refused. The config payload bound is now sized from its key count. Release 0.3.34.

Timelines: family | ancestors | descendants | both | trunk | version-0.3.34
Files: files | file ages | folders
SHA3-256: 5fce7e867dfdae07cbfc3318811cc23090336e7a3d10cf0fccba51de97dd9ac0
User & Date: dmestas on 2026-09-28 16:44:53.346
Other Links: manifest | tags
Context
2026-09-28
19:37
Lock notices append to a redirected stderr instead of overwriting it check-in: d59b4a1827 user: dmestas tags: trunk
16:44
zit git export/status: a remembered Git mirror with autopush

git export exports into MIRROR and remembers it, with an autopush URL, push branch and email domain, in repository config; a bare re-run does the round trip. Authors' addresses come from their user-table contact, set with the new users contact. Autopush URLs carrying a password are refused. The config payload bound is now sized from its key count. Release 0.3.34. check-in: 5fce7e867d user: dmestas tags: trunk, version-0.3.34

12:53
pack, shun --force: fsync the directory after the rename; model it in DST

The rename that installs a new generation was never made durable, so a power loss after a reported success could bring the old store back, and with it content a shun had removed. The fault layer now reverts creates, renames and deletes no directory fsync made durable, and the shun sweep requires a rewrite that succeeded to survive a power cut. check-in: 3873759cfa user: dmestas tags: trunk

Changes