Fossil SCM

Added a new doc, "Fossil and the CAP Theorem." It distills some good info from the forum, so we can just point at it instead of recapitulating it. But it's being checked in now because an upcoming commit will refer to it.

wyoung 2020-10-05 17:02 trunk
Commit 3ddd56d0b03d83c3a02c9c707922f698e9e88c9b774fc782bf16f26734f950fc
Parent e0a38eb3eb67c7c…
3 files changed +138 +1 +3
+ www/cap-theorem.md ~ www/mkindex.tcl ~ www/permutedindex.html
A www/cap-theorem.md
+138
--- a/www/cap-theorem.md
+++ b/www/cap-theorem.md
@@ -0,0 +1,138 @@
1
+# Fossil and the CAP Theorem
2
+
3
+[The CAP theorem][cap] is a fundamental mathematical proof about
4
+distributed systems. A software system can no more get around it than a
5
+physical system can get past *c*, the [speed of light][sol] constant.
6
+
7
+Fossil is a distributed system, so it can be useful to think about it in
8
+terms of the CAP theorem. We won’t discuss the theorem itself or how you
9
+reason using its results here. For that, we recommend [this article][tut].
10
+
11
+[cap]: https://en.wikipedia.org/wiki/CAP_theorem
12
+[sol]: https://en.wikipedia.org/wiki/Speed_of_light
13
+[tut]: https://www.ibm.com-theorem
14
+
15
+
16
+<a id="ap"></a>
17
+## Fossil Is an AP-Mode System
18
+
19
+As with all common [DVCSes][dvcs], Fossil is an AP-mode system, meaning
20
+that your local clone isn’t necessarily consistent with all other clones
21
+(C), but the system is always available for use (A) and
22
+partition-tolerant (P). This is what allows you to turn off Fossil’s
23
+autosync mode, go off-network, and continue working with Fossil, even
24
+though only a single node (your local repo clone) is accessible at the
25
+time.
26
+
27
+You may consider that going back online restores “C”, because upon sync,
28
+you’re now consistent with the repo you cloned from. But, if another
29
+user has gone offline in the meantime, and they’ve made commits to their
30
+disconnected repo, *you* aren’t consistent with *them.*istency across the network.
31
+
32
+There’s no getting around the CAP theorem!
33
+
34
+[dvcs]: https:_control
35
+
36
+
37
+<a id="ca"></a>
38
+## CA-Mode Fossil
39
+
40
+What would it mean to redesign Fossil to be CA-mode?
41
+
42
+It means we get a system that is always consistent (C) and available (A)
43
+as long as there are no partitions (P).
44
+
45
+That’s basically [CVS] and [Subversion][svn]: youas long as your connection to the central repo server functions.
46
+
47
+It’s rather trivial to talk about single-point-of-failure systems ems like
48
+CVS or Subversion as
49
+CA-mode. Another common example used this way is a classical RDBMS, but
50
+aren’t we here to talk about distributed systems? What’s a good example
51
+of a *distributed* CA-mode system?
52
+
53
+A better example is [Kafka], which in its default configuration assumes
54
+it being run on a corporate LAN in a single datan its application of CArking with Fossil, even
55
+though only a single node (your local repo clone) is accessible at the
56
+time.
57
+
58
+You may consider that going back online restP Theorem
59
+
60
+[The CAP theorem][cap] is a fundamental mathematical proof about
61
+distributed systems. A software system can no more get around it than a
62
+physical system can get past *c*, the [speed of light][sol] constant.
63
+
64
+Fossil is a distributed system, so it can be useful to think about it in
65
+terms of the CAP theorem. We won’t discuss the theorem itself or how you
66
+reason using its results here. For that, we recommend [this article][tut].
67
+
68
+[cap]: https://en.wikipedia.org/wiki/CAP_theorem
69
+[sol]: https://en.wikipedia.org/wiki/Speed_of_light
70
+[tut]: https://www.ibm.com/cloud/learn/cap-theorem
71
+
72
+
73
+<a id="ap"></a>
74
+## Fossil Is an AP-Mode System
75
+
76
+As with all common [DVCSes][dvcs], Fossil is an AP-mode system, meaning
77
+that your local clone isn’t necessarily consistent with all other clones
78
+(C), but the system is always available for use (A) and
79
+partition-tolerant (P). This is what allows you to turn off Fossil’s
80
+autosync mode, go off-network, and continue working with Fossil, even
81
+though only a single node (your local repo clone) is accessible at the
82
+time.
83
+
84
+You may consider that going back online restores “C”, because upon sync,
85
+you’re now consistent with the repo you cloned from. But, if another
86
+user has gone offline in t## CProl
87
+
88
+
89
+<a id="ca"></mple used this way is a classical RDBMS, but
90
+aren’t we here to talk about distributed systems? What’s a good example
91
+of a *distributed* CA-mode system?
92
+
93
+A better example is [Kafka], which in its default configuration assumes
94
+it being run on a corporate LAN in a single datan its application of CArking with Fossil, even
95
+though only a single node (your local repo clone) is accessible at the
96
+time.
97
+
98
+You may consider that going back online restP Theorem
99
+
100
+[The CAP theorem][cap] is a fundamental mathematical proof about
101
+distributed systems. A software system can no more get around it than a
102
+physical system can get past *c*, the [speed of light][sol] constant.
103
+
104
+Fossil is a distributed system, so it can be useful to think about it in
105
+terms of the CAP theorem. We won’t discuss the theorem itself or how you
106
+reason using its results here. For that, we recommend [this article][tut].
107
+
108
+[cap]: https://en.wikipedia.org/wiki/CAP_theorem
109
+[sol]: https://en.wikipedia.org/wiki/Speed_of_light
110
+[tut]: https://www.ibm.com/cloud/learn/cap-theorem
111
+
112
+
113
+<a id="ap"></a>
114
+## Fossil Is an AP-Mode System
115
+
116
+As with all common [DVCSes][dvcs], Fossil is an AP-mode system, meaning
117
+that your local clone isn’t necessarily consistent with all other clones
118
+(C), but the system is always available for use (A) and
119
+partition-tolerant (P). This is what allows you to turn off Fossil’s
120
+autosync mode, go off-network, and continue working with Fossil, even
121
+though only a single node (your local repo clone) is accessible at the
122
+time.
123
+
124
+You may consider that going back online restores “C”, because upon sync,
125
+you’re now consistent with the repo you cloned from. But, if another
126
+user has gone offline in the meantime, and they’ve made commits to their
127
+disconnected repo, *you* aren’t consistent with *them.* Besides which,
128
+if another user commits to the central repo, that doesn’t push the
129
+change down to you automatically: even if all users of a Fossil system
130
+are online at the same instant, and they’re all using autosync, Fossil
131
+doesn’t guarantee consistency across the network.
132
+
133
+There’s no getting around the CAP theorem!
134
+
135
+[dvcs]: https://en.# Fossil and the when there aren’t enough active servers or warm
136
+spares to promote to active status.
137
+
138
+CP is your classical [BFT
--- a/www/cap-theorem.md
+++ b/www/cap-theorem.md
@@ -0,0 +1,138 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/cap-theorem.md
+++ b/www/cap-theorem.md
@@ -0,0 +1,138 @@
1 # Fossil and the CAP Theorem
2
3 [The CAP theorem][cap] is a fundamental mathematical proof about
4 distributed systems. A software system can no more get around it than a
5 physical system can get past *c*, the [speed of light][sol] constant.
6
7 Fossil is a distributed system, so it can be useful to think about it in
8 terms of the CAP theorem. We won’t discuss the theorem itself or how you
9 reason using its results here. For that, we recommend [this article][tut].
10
11 [cap]: https://en.wikipedia.org/wiki/CAP_theorem
12 [sol]: https://en.wikipedia.org/wiki/Speed_of_light
13 [tut]: https://www.ibm.com-theorem
14
15
16 <a id="ap"></a>
17 ## Fossil Is an AP-Mode System
18
19 As with all common [DVCSes][dvcs], Fossil is an AP-mode system, meaning
20 that your local clone isn’t necessarily consistent with all other clones
21 (C), but the system is always available for use (A) and
22 partition-tolerant (P). This is what allows you to turn off Fossil’s
23 autosync mode, go off-network, and continue working with Fossil, even
24 though only a single node (your local repo clone) is accessible at the
25 time.
26
27 You may consider that going back online restores “C”, because upon sync,
28 you’re now consistent with the repo you cloned from. But, if another
29 user has gone offline in the meantime, and they’ve made commits to their
30 disconnected repo, *you* aren’t consistent with *them.*istency across the network.
31
32 There’s no getting around the CAP theorem!
33
34 [dvcs]: https:_control
35
36
37 <a id="ca"></a>
38 ## CA-Mode Fossil
39
40 What would it mean to redesign Fossil to be CA-mode?
41
42 It means we get a system that is always consistent (C) and available (A)
43 as long as there are no partitions (P).
44
45 That’s basically [CVS] and [Subversion][svn]: youas long as your connection to the central repo server functions.
46
47 It’s rather trivial to talk about single-point-of-failure systems ems like
48 CVS or Subversion as
49 CA-mode. Another common example used this way is a classical RDBMS, but
50 aren’t we here to talk about distributed systems? What’s a good example
51 of a *distributed* CA-mode system?
52
53 A better example is [Kafka], which in its default configuration assumes
54 it being run on a corporate LAN in a single datan its application of CArking with Fossil, even
55 though only a single node (your local repo clone) is accessible at the
56 time.
57
58 You may consider that going back online restP Theorem
59
60 [The CAP theorem][cap] is a fundamental mathematical proof about
61 distributed systems. A software system can no more get around it than a
62 physical system can get past *c*, the [speed of light][sol] constant.
63
64 Fossil is a distributed system, so it can be useful to think about it in
65 terms of the CAP theorem. We won’t discuss the theorem itself or how you
66 reason using its results here. For that, we recommend [this article][tut].
67
68 [cap]: https://en.wikipedia.org/wiki/CAP_theorem
69 [sol]: https://en.wikipedia.org/wiki/Speed_of_light
70 [tut]: https://www.ibm.com/cloud/learn/cap-theorem
71
72
73 <a id="ap"></a>
74 ## Fossil Is an AP-Mode System
75
76 As with all common [DVCSes][dvcs], Fossil is an AP-mode system, meaning
77 that your local clone isn’t necessarily consistent with all other clones
78 (C), but the system is always available for use (A) and
79 partition-tolerant (P). This is what allows you to turn off Fossil’s
80 autosync mode, go off-network, and continue working with Fossil, even
81 though only a single node (your local repo clone) is accessible at the
82 time.
83
84 You may consider that going back online restores “C”, because upon sync,
85 you’re now consistent with the repo you cloned from. But, if another
86 user has gone offline in t## CProl
87
88
89 <a id="ca"></mple used this way is a classical RDBMS, but
90 aren’t we here to talk about distributed systems? What’s a good example
91 of a *distributed* CA-mode system?
92
93 A better example is [Kafka], which in its default configuration assumes
94 it being run on a corporate LAN in a single datan its application of CArking with Fossil, even
95 though only a single node (your local repo clone) is accessible at the
96 time.
97
98 You may consider that going back online restP Theorem
99
100 [The CAP theorem][cap] is a fundamental mathematical proof about
101 distributed systems. A software system can no more get around it than a
102 physical system can get past *c*, the [speed of light][sol] constant.
103
104 Fossil is a distributed system, so it can be useful to think about it in
105 terms of the CAP theorem. We won’t discuss the theorem itself or how you
106 reason using its results here. For that, we recommend [this article][tut].
107
108 [cap]: https://en.wikipedia.org/wiki/CAP_theorem
109 [sol]: https://en.wikipedia.org/wiki/Speed_of_light
110 [tut]: https://www.ibm.com/cloud/learn/cap-theorem
111
112
113 <a id="ap"></a>
114 ## Fossil Is an AP-Mode System
115
116 As with all common [DVCSes][dvcs], Fossil is an AP-mode system, meaning
117 that your local clone isn’t necessarily consistent with all other clones
118 (C), but the system is always available for use (A) and
119 partition-tolerant (P). This is what allows you to turn off Fossil’s
120 autosync mode, go off-network, and continue working with Fossil, even
121 though only a single node (your local repo clone) is accessible at the
122 time.
123
124 You may consider that going back online restores “C”, because upon sync,
125 you’re now consistent with the repo you cloned from. But, if another
126 user has gone offline in the meantime, and they’ve made commits to their
127 disconnected repo, *you* aren’t consistent with *them.* Besides which,
128 if another user commits to the central repo, that doesn’t push the
129 change down to you automatically: even if all users of a Fossil system
130 are online at the same instant, and they’re all using autosync, Fossil
131 doesn’t guarantee consistency across the network.
132
133 There’s no getting around the CAP theorem!
134
135 [dvcs]: https://en.# Fossil and the when there aren’t enough active servers or warm
136 spares to promote to active status.
137
138 CP is your classical [BFT
M www/mkindex.tcl
+1
--- www/mkindex.tcl
+++ www/mkindex.tcl
@@ -18,10 +18,11 @@
1818
 blame.wiki {The Annotate/Blame Algorithm Of Fossil}
1919
 blockchain.md {Fossil As Blockchain}
2020
 branching.wiki {Branching, Forking, Merging, and Tagging}
2121
 bugtheory.wiki {Bug Tracking In Fossil}
2222
 build.wiki {Compiling and Installing Fossil}
23
+ cap-theorem.md {Fossil and the CAP Theorem}
2324
 caps/ {Administering User Capabilities}
2425
 caps/admin-v-setup.md {Differences Between Setup and Admin Users}
2526
 caps/ref.html {User Capability Reference}
2627
 cgi.wiki {CGI Script Configuration Options}
2728
 changes.wiki {Fossil Changelog}
2829
--- www/mkindex.tcl
+++ www/mkindex.tcl
@@ -18,10 +18,11 @@
18 blame.wiki {The Annotate/Blame Algorithm Of Fossil}
19 blockchain.md {Fossil As Blockchain}
20 branching.wiki {Branching, Forking, Merging, and Tagging}
21 bugtheory.wiki {Bug Tracking In Fossil}
22 build.wiki {Compiling and Installing Fossil}
 
23 caps/ {Administering User Capabilities}
24 caps/admin-v-setup.md {Differences Between Setup and Admin Users}
25 caps/ref.html {User Capability Reference}
26 cgi.wiki {CGI Script Configuration Options}
27 changes.wiki {Fossil Changelog}
28
--- www/mkindex.tcl
+++ www/mkindex.tcl
@@ -18,10 +18,11 @@
18 blame.wiki {The Annotate/Blame Algorithm Of Fossil}
19 blockchain.md {Fossil As Blockchain}
20 branching.wiki {Branching, Forking, Merging, and Tagging}
21 bugtheory.wiki {Bug Tracking In Fossil}
22 build.wiki {Compiling and Installing Fossil}
23 cap-theorem.md {Fossil and the CAP Theorem}
24 caps/ {Administering User Capabilities}
25 caps/admin-v-setup.md {Differences Between Setup and Admin Users}
26 caps/ref.html {User Capability Reference}
27 cgi.wiki {CGI Script Configuration Options}
28 changes.wiki {Fossil Changelog}
29
M www/permutedindex.html
+3
--- www/permutedindex.html
+++ www/permutedindex.html
@@ -47,10 +47,11 @@
4747
 <li><a href="antibot.wiki">Bots &mdash; Defense against Spiders and</a></li>
4848
 <li><a href="private.wiki">Branches &mdash; Creating, Syncing, and Deleting Private</a></li>
4949
 <li><a href="branching.wiki"><b>Branching, Forking, Merging, and Tagging</b></a></li>
5050
 <li><a href="bugtheory.wiki"><b>Bug Tracking In Fossil</b></a></li>
5151
 <li><a href="makefile.wiki">Build Process &mdash; The Fossil</a></li>
52
+<li><a href="cap-theorem.md">CAP Theorem &mdash; Fossil and the</a></li>
5253
 <li><a href="caps/">Capabilities &mdash; Administering User</a></li>
5354
 <li><a href="caps/ref.html">Capability Reference &mdash; User</a></li>
5455
 <li><a href="cgi.wiki"><b>CGI Script Configuration Options</b></a></li>
5556
 <li><a href="serverext.wiki">CGI Scripts &mdash; Adding Extensions To A Fossil Server Using</a></li>
5657
 <li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li>
@@ -124,10 +125,11 @@
124125
 <li><a href="fileformat.wiki">Format &mdash; Fossil File</a></li>
125126
 <li><a href="image-format-vs-repo-size.md">Format vs Fossil Repo Size &mdash; Image</a></li>
126127
 <li><a href="../../../md_rules">Formatting Rules &mdash; Markdown</a></li>
127128
 <li><a href="../../../wiki_rules">Formatting Rules &mdash; Wiki</a></li>
128129
 <li><a href="forum.wiki">Forums &mdash; Fossil</a></li>
130
+<li><a href="cap-theorem.md"><b>Fossil and the CAP Theorem</b></a></li>
129131
 <li><a href="blockchain.md"><b>Fossil As Blockchain</b></a></li>
130132
 <li><a href="changes.wiki"><b>Fossil Changelog</b></a></li>
131133
 <li><a href="concepts.wiki"><b>Fossil Core Concepts</b></a></li>
132134
 <li><a href="css-tricks.md"><b>Fossil CSS Tips and Tricks</b></a></li>
133135
 <li><a href="delta_encoder_algorithm.wiki"><b>Fossil Delta Encoding Algorithm</b></a></li>
@@ -300,10 +302,11 @@
300302
 <li><a href="webui.wiki"><b>The Fossil Web Interface</b></a></li>
301303
 <li><a href="history.md"><b>The Purpose And History Of Fossil</b></a></li>
302304
 <li><a href="th1.md"><b>The TH1 Scripting Language</b></a></li>
303305
 <li><a href="customskin.md"><b>Theming: Customizing The Appearance of Web Pages</b></a></li>
304306
 <li><a href="customgraph.md"><b>Theming: Customizing the Timeline Graph</b></a></li>
307
+<li><a href="cap-theorem.md">Theorem &mdash; Fossil and the CAP</a></li>
305308
 <li><a href="theory1.wiki"><b>Thoughts On The Design Of The Fossil DVCS</b></a></li>
306309
 <li><a href="custom_ticket.wiki">Ticket System &mdash; Customizing The</a></li>
307310
 <li><a href="tickets.wiki">Ticket System &mdash; The Fossil</a></li>
308311
 <li><a href="customgraph.md">Timeline Graph &mdash; Theming: Customizing the</a></li>
309312
 <li><a href="css-tricks.md">Tips and Tricks &mdash; Fossil CSS</a></li>
310313
--- www/permutedindex.html
+++ www/permutedindex.html
@@ -47,10 +47,11 @@
47 <li><a href="antibot.wiki">Bots &mdash; Defense against Spiders and</a></li>
48 <li><a href="private.wiki">Branches &mdash; Creating, Syncing, and Deleting Private</a></li>
49 <li><a href="branching.wiki"><b>Branching, Forking, Merging, and Tagging</b></a></li>
50 <li><a href="bugtheory.wiki"><b>Bug Tracking In Fossil</b></a></li>
51 <li><a href="makefile.wiki">Build Process &mdash; The Fossil</a></li>
 
52 <li><a href="caps/">Capabilities &mdash; Administering User</a></li>
53 <li><a href="caps/ref.html">Capability Reference &mdash; User</a></li>
54 <li><a href="cgi.wiki"><b>CGI Script Configuration Options</b></a></li>
55 <li><a href="serverext.wiki">CGI Scripts &mdash; Adding Extensions To A Fossil Server Using</a></li>
56 <li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li>
@@ -124,10 +125,11 @@
124 <li><a href="fileformat.wiki">Format &mdash; Fossil File</a></li>
125 <li><a href="image-format-vs-repo-size.md">Format vs Fossil Repo Size &mdash; Image</a></li>
126 <li><a href="../../../md_rules">Formatting Rules &mdash; Markdown</a></li>
127 <li><a href="../../../wiki_rules">Formatting Rules &mdash; Wiki</a></li>
128 <li><a href="forum.wiki">Forums &mdash; Fossil</a></li>
 
129 <li><a href="blockchain.md"><b>Fossil As Blockchain</b></a></li>
130 <li><a href="changes.wiki"><b>Fossil Changelog</b></a></li>
131 <li><a href="concepts.wiki"><b>Fossil Core Concepts</b></a></li>
132 <li><a href="css-tricks.md"><b>Fossil CSS Tips and Tricks</b></a></li>
133 <li><a href="delta_encoder_algorithm.wiki"><b>Fossil Delta Encoding Algorithm</b></a></li>
@@ -300,10 +302,11 @@
300 <li><a href="webui.wiki"><b>The Fossil Web Interface</b></a></li>
301 <li><a href="history.md"><b>The Purpose And History Of Fossil</b></a></li>
302 <li><a href="th1.md"><b>The TH1 Scripting Language</b></a></li>
303 <li><a href="customskin.md"><b>Theming: Customizing The Appearance of Web Pages</b></a></li>
304 <li><a href="customgraph.md"><b>Theming: Customizing the Timeline Graph</b></a></li>
 
305 <li><a href="theory1.wiki"><b>Thoughts On The Design Of The Fossil DVCS</b></a></li>
306 <li><a href="custom_ticket.wiki">Ticket System &mdash; Customizing The</a></li>
307 <li><a href="tickets.wiki">Ticket System &mdash; The Fossil</a></li>
308 <li><a href="customgraph.md">Timeline Graph &mdash; Theming: Customizing the</a></li>
309 <li><a href="css-tricks.md">Tips and Tricks &mdash; Fossil CSS</a></li>
310
--- www/permutedindex.html
+++ www/permutedindex.html
@@ -47,10 +47,11 @@
47 <li><a href="antibot.wiki">Bots &mdash; Defense against Spiders and</a></li>
48 <li><a href="private.wiki">Branches &mdash; Creating, Syncing, and Deleting Private</a></li>
49 <li><a href="branching.wiki"><b>Branching, Forking, Merging, and Tagging</b></a></li>
50 <li><a href="bugtheory.wiki"><b>Bug Tracking In Fossil</b></a></li>
51 <li><a href="makefile.wiki">Build Process &mdash; The Fossil</a></li>
52 <li><a href="cap-theorem.md">CAP Theorem &mdash; Fossil and the</a></li>
53 <li><a href="caps/">Capabilities &mdash; Administering User</a></li>
54 <li><a href="caps/ref.html">Capability Reference &mdash; User</a></li>
55 <li><a href="cgi.wiki"><b>CGI Script Configuration Options</b></a></li>
56 <li><a href="serverext.wiki">CGI Scripts &mdash; Adding Extensions To A Fossil Server Using</a></li>
57 <li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li>
@@ -124,10 +125,11 @@
125 <li><a href="fileformat.wiki">Format &mdash; Fossil File</a></li>
126 <li><a href="image-format-vs-repo-size.md">Format vs Fossil Repo Size &mdash; Image</a></li>
127 <li><a href="../../../md_rules">Formatting Rules &mdash; Markdown</a></li>
128 <li><a href="../../../wiki_rules">Formatting Rules &mdash; Wiki</a></li>
129 <li><a href="forum.wiki">Forums &mdash; Fossil</a></li>
130 <li><a href="cap-theorem.md"><b>Fossil and the CAP Theorem</b></a></li>
131 <li><a href="blockchain.md"><b>Fossil As Blockchain</b></a></li>
132 <li><a href="changes.wiki"><b>Fossil Changelog</b></a></li>
133 <li><a href="concepts.wiki"><b>Fossil Core Concepts</b></a></li>
134 <li><a href="css-tricks.md"><b>Fossil CSS Tips and Tricks</b></a></li>
135 <li><a href="delta_encoder_algorithm.wiki"><b>Fossil Delta Encoding Algorithm</b></a></li>
@@ -300,10 +302,11 @@
302 <li><a href="webui.wiki"><b>The Fossil Web Interface</b></a></li>
303 <li><a href="history.md"><b>The Purpose And History Of Fossil</b></a></li>
304 <li><a href="th1.md"><b>The TH1 Scripting Language</b></a></li>
305 <li><a href="customskin.md"><b>Theming: Customizing The Appearance of Web Pages</b></a></li>
306 <li><a href="customgraph.md"><b>Theming: Customizing the Timeline Graph</b></a></li>
307 <li><a href="cap-theorem.md">Theorem &mdash; Fossil and the CAP</a></li>
308 <li><a href="theory1.wiki"><b>Thoughts On The Design Of The Fossil DVCS</b></a></li>
309 <li><a href="custom_ticket.wiki">Ticket System &mdash; Customizing The</a></li>
310 <li><a href="tickets.wiki">Ticket System &mdash; The Fossil</a></li>
311 <li><a href="customgraph.md">Timeline Graph &mdash; Theming: Customizing the</a></li>
312 <li><a href="css-tricks.md">Tips and Tricks &mdash; Fossil CSS</a></li>
313

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button