Overview
| Comment: | land protected-branches |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
caaa75e5e63ab98ea070fb6e5438531a |
| User & Date: | dmestas on 2026-08-26 13:45:39.236 |
| Other Links: | manifest | tags |
Context
|
2026-08-26
| ||
| 13:49 | Accepted. The pattern hid two pages; the panel showed which one was slow once it stopped showing the pattern. check-in: 7ec507a60e user: dmestas tags: trunk | |
| 13:45 | land protected-branches check-in: caaa75e5e6 user: dmestas tags: trunk | |
| 13:41 |
RFC 0007: protected branches — ownership enforced where identity is a fact
A check-in joins a protected branch only by an owner's hand; accepting a landing on it follows from that rather than being a second rule. Policy lives in OLTP beside caps, is evaluated at the xfer gate and the accept op, and writes nothing to the repository — fossil compatibility is a normative section, not a hope. The one zit change is drafted in Appendix A. check-in: d4cf4acf26 user: dmestas tags: protected-branches | |
| 13:37 | Accepted. Clicking through found what testing the parts did not. check-in: 111491a3a9 user: dmestas tags: trunk | |
Changes
Added docs/rfcs/0007-protected-branches.md version [32aad3d0be].