1 \section{Commit annotation}
3 We annotate each Topbloke commit $C$ with:
7 \baseof{C}, \text{ if } C \in \pay{C}
10 \text{ either } C \haspatch \p \text{ or } C \nothaspatch \p
12 \bigforall_{\py \not\ni C} \pendsof{C}{\py}
15 $\patchof{C}$, for each kind of Topbloke-generated commit, is stated
16 in the summary in the section for that kind of commit.
18 Whether $\baseof{C}$ is required, and if so what the value is, is
19 stated in the proof of Unique Base for each kind of commit.
21 $C \haspatch \p$ or $\nothaspatch \p$ is represented as a
22 list of $\p$ for which $C \haspatch \p$;
23 for any $\p$ not listed, $C \nothaspatch \p$.
24 Whether to record $C \haspatch \p$ in a new commit
26 (in terms of $I \haspatch \p$ or $I \nothaspatch \p$
27 for the ingredients $I$)
28 in the proof of Coherence for each kind of commit.
30 $\pendsof{C}{\py}$ is computed, for all Topbloke-generated commits,
31 using the lemma Calculation of Ends, above.
32 We do not annotate $\pendsof{C}{\pay{C}}$ for $C \in \pay{C}$. Doing so would
33 make it wrong to make plain commits with git because the recorded $\pends$
34 would have to be updated. The annotation is not needed in that case
35 because $\forall_{\pay{C} \ni C} \; \pendsof{C}{\pay{C}} = \{C\}$.