Fossil SCM

Extracted the checkout workflows section of the gitusers.md doc to a new www/ckout-workflows.md doc, which talks about Git only as a common comparison. Linking to it from the gitusers.md doc, which now only talks about the Git-specific bits we had in that section.

wyoung 2020-11-01 23:35 trunk

Commit b6b1b705d001178bcc88438f6fbd314d6f75dedf8b5851fed32133089a8529e5

Parent 54001a4efef57c3…

4 files changed +33 +15 -113 +1 +2

+ www/ckout-workflows.md ~ www/gitusers.md ~ www/mkindex.tcl ~ www/permutedindex.html

A www/ckout-workflows.md

+33

		--- a/www/ckout-workflows.md
		+++ b/www/ckout-workflows.md
		@@ -0,0 +1,33 @@
	1	+# Check-Out WorWith Fossil 2.14 �# Check-Out Workflows
	2	+
	3	+Be # Check-Out Workflows
	4	+
	5	+Because Fossil separates the concept of “check-out d e Fossil separates the concept of “check-out d , leaving its `git-workWith Git’s typicalFossil working model,
	6	+With the clone done as in [the prior section](#mdw), the most idiomatic
	7	+The Clone-and-Open Wayhat allows you to get clbehavior:
	8	+The use of [`fossil openclone`][clone]
	9	+is likely to surprise a Git user. When we were [discussing][caod]
	10	+this, we considered following the Git command style, but we decided
	11	+against it because it goes against this core Fossil design principle:
	12	+given that the Fossil repo is separate from the check-out, why would you
	13	+expect asking for a repo clone to also create a check-out directory for
	14	+you? We view commingled repository + check-out as a design error in
	15	+Git, so why would we repeat the error?
	16	+
	17	+To see why we see this behavior is error-prone, consider that
	18	+`git clean` must have an exception to avoid nuking the `.git` directory.
	19	+We had to add that complication to `fossil clean` when we added the
	20	+`fossil open URI` feature: it won’t nuke the repo DB file.
	21	+
	22	+[clone]: /help?cmd=clone
	23	+[open]: /help?cmd=openThe Git Clone Way
	24	+
	25	+This feature didn’t placate many Git fans, though, so w# Check-Out WorWithi# Check-Out WorWith Fossil 2# Check-Out Wokflows
	26	+
	27	+Because Fossil separates the concept of “check-out d e Fossil separates the concept of “check-out d # Check-Out WorWik-Out Workflows
	28	+
	29	+Because Fossil separates the concept of “check-out d e Fossil separates the concept of “check-out d # Check-Out WorWith Fossil 2.14 �# Check-Out Workflows
	30	+
	31	+Be # Check-Out Workflows
	32	+
	33	+Because Fossil separates the concept of “check-out d e Fossil separates the concept of “check-out d rum/forumpost/3f143cec74

	--- a/www/ckout-workflows.md
	+++ b/www/ckout-workflows.md
	@@ -0,0 +1,33 @@

	--- a/www/ckout-workflows.md
	+++ b/www/ckout-workflows.md
	@@ -0,0 +1,33 @@
1	# Check-Out WorWith Fossil 2.14 �# Check-Out Workflows
2
3	Be # Check-Out Workflows
4
5	Because Fossil separates the concept of “check-out d e Fossil separates the concept of “check-out d , leaving its `git-workWith Git’s typicalFossil working model,
6	With the clone done as in [the prior section](#mdw), the most idiomatic
7	The Clone-and-Open Wayhat allows you to get clbehavior:
8	The use of [`fossil openclone`][clone]
9	is likely to surprise a Git user. When we were [discussing][caod]
10	this, we considered following the Git command style, but we decided
11	against it because it goes against this core Fossil design principle:
12	given that the Fossil repo is separate from the check-out, why would you
13	expect asking for a repo clone to also create a check-out directory for
14	you? We view commingled repository + check-out as a design error in
15	Git, so why would we repeat the error?
16
17	To see why we see this behavior is error-prone, consider that
18	`git clean` must have an exception to avoid nuking the `.git` directory.
19	We had to add that complication to `fossil clean` when we added the
20	`fossil open URI` feature: it won’t nuke the repo DB file.
21
22	[clone]: /help?cmd=clone
23	[open]: /help?cmd=openThe Git Clone Way
24
25	This feature didn’t placate many Git fans, though, so w# Check-Out WorWithi# Check-Out WorWith Fossil 2# Check-Out Wokflows
26
27	Because Fossil separates the concept of “check-out d e Fossil separates the concept of “check-out d # Check-Out WorWik-Out Workflows
28
29	Because Fossil separates the concept of “check-out d e Fossil separates the concept of “check-out d # Check-Out WorWith Fossil 2.14 �# Check-Out Workflows
30
31	Be # Check-Out Workflows
32
33	Because Fossil separates the concept of “check-out d e Fossil separates the concept of “check-out d rum/forumpost/3f143cec74

M www/gitusers.md

+15 -113

		--- www/gitusers.md
		+++ www/gitusers.md
		@@ -95,122 +95,25 @@
95	95
96	96	On a Windows box, you might instead choose "`C:\Fossils`"
97	97	and do without the subdirectory scheme, for example.
98	98
99	99
100		-#### <a id="scw"></a> Single-Checkout Workflows
101		-
102		-The most idiomatic way to use Fossil in the typical Git way — switching
103		-between versions in a single check-out directory — is as follows:
104		-
105		- fossil clone https://example.com/repo /path/to/repo.fossil
106		- mkdir work-dir
107		- cd work-dir
108		- fossil open /path/to/repo.fossil
109		- ...work on trunk...
110		- fossil update my-other-branch # like “git checkout”
111		- ...work on your other branch in the same directory...
112		-
113		-In Fossil 2.12, we added a feature that allows you to get closer to
114		-Git’s single-step clone-and-open behavior:
115		-
116		- mkdir work-dir
117		- cd work-dir
118		- fossil open https://example.com/repo
119		-
120		-Now you have “trunk” open in `work-dir`, with the repo file stored as
121		-`repo.fossil` in that same directory.
122		-
123		-The use of [`fossil open`][open] here instead of [`fossil clone`][clone]
124		-likely surprises you as a Git user. When we were [discussing][caod]
125		-this, we considered following the Git command style, but we decided
126		-against it because it goes against this core Fossil design principle:
127		-given that the Fossil repo is separate from the check-out, why would you
128		-expect asking for a repo clone to also create a check-out directory for
129		-you? We view commingled repository + check-out as a design error in
130		-Git, so why would we repeat the error?
131		-
132		-To see why we see this behavior is error-prone, consider that
133		-`git clean` must have an exception to avoid nuking the `.git` directory.
134		-We had to add that complication to `fossil clean` when we added the
135		-`fossil open URI` feature: it won’t nuke the repo DB file.
136		-
137		-This feature didn’t placate many Git fans, though, so with Fossil 2.14 —
138		-currently unreleased — we now allow this:
139		-
140		- fossil clone https://fossil-scm.org/fossil
141		-
142		-This results in a `fossil.fossil` repo DB file and a `fossil/` working
143		-directory.
144		-
145		-Note that our `clone URI` behavior does not commingle the repo and
146		-check-out, solving our major problem with the Git design, though we
147		-still believe it to be confusing to have “clone” be part of “open,” and
148		-still more confusing to have “open” part of “clone.” We prefer keeping
149		-these operations entirely separate, either as at the [top of this
150		-section](#scw) or [as in the next one](#mcw). Still, please yourself.
151		-
152		-If you want the repo to be named something else, adjust the URL:
153		-
154		- fossil clone https://fossil-scm.org/fossil/fsl
155		-
156		-That gets you `fsl.fossil` checked out into `fsl/`.
157		-
158		-For sites where the repo isn’t served from a subdirectory like this, you
159		-might need another form of the URL. For example, you might have your
160		-repo served from `dev.example.com` and want it cloned as `my-project`:
161		-
162		- fossil clone https://dev.example.com/repo/my-project
163		-
164		-The `/repo` addition is the key: whatever comes after is used as the
165		-repository name. [See the docs][clone] for more details.
166		-
167		-[caod]: https://fossil-scm.org/forum/forumpost/3f143cec74
168		-
169		-
170		-#### <a id="mcw"></a> Multiple-Checkout Workflows
171		-
172		-Because Fossil cleanly separates the repository from the check-out, it
173		-is routine to have multiple check-outs from the same repository:
174		-
175		- mkdir -p ~/src/my-project/trunk
176		- cd ~/src/my-project/trunk
177		- fossil open /path/to/repo.fossil # implicitly opens “trunk”
178		- mkdir ../my-other-branch
179		- cd ../my-other-branch
180		- fossil open /path/to/repo.fossil my-other-branch
181		- mkdir ../release
182		- cd ../release
183		- fossil open /path/to/repo.fossil release
184		- mkdir ../scratch
185		- cd ../scratch
186		- fossil open /path/to/repo.fossil abcd1234
187		- mkdir ../test
188		- cd ../test
189		- fossil open /path/to/repo.fossil 2019-04-01
190		-
191		-Now you have five separate check-out directories: one each for trunk, an
192		-alternate branch you’re working on, the latest tagged public release, a
193		-“scratch” directory for experiments or brief bits of work you don’t want
194		-to do in the other check-out directories, and a directory for testing a
195		-user report of a bug in the trunk version as of last April Fool’s Day.
196		-Each check-out operates independently of the others.
197		-
198		-This multiple-checkouts working style is especially useful when Fossil stores source code in programming languages
199		-where there is a “build” step that transforms source files into files
200		-you actually run or distribute. With Git’s typical switch-in-place workflow,
201		-you have to rebuild all outputs from the source files
202		-that differ between those versions whenever you switch versions. In the above Fossil working model,
203		-you switch versions with a “`cd`” command instead, so that you only have
204		-to rebuild outputs from files you yourself change.
205		-
206		-This style is also useful when a check-out directory may be tied up with
207		-some long-running process, as with the “test” example above, where you
208		-might need to run an hours-long brute-force replication script to tickle
209		-a [Heisenbug][hb], forcing it to show itself. While that runs, you can
210		-open a new terminal tab, “`cd ../trunk`”, and get back
211		-to work.
	100	+#### <a id="cwork" name="scw"></a> Checkout Workflows
	101	+
	102	+This is a complicated topic, so we [cover it elsewhere][cw].
	103	+
	104	+The main Git-specific thing to add to that document is that this:
	105	+
	106	+ git checkout some-branch
	107	+
	108	+…is spelled:
	109	+
	110	+ fossil update some-branch
	111	+
	112	+…in Fossil.
	113	+
	114	+[cw]: ./ckout-workflows.md
212	115
213	116
214	117	#### <a id="close" name="dotfile"></a> Closing A Check-Out
215	118
216	119	The `fossil close` command dissaociates a check-out directory from the
		@@ -287,11 +190,10 @@
287	190
288	191
289	192	[clone]: /help?cmd=clone
290	193	[close]: /help?cmd=close
291	194	[gloss]: ./whyusefossil.wiki#definitions
292		-[hb]: https://en.wikipedia.org/wiki/Heisenbug
293	195	[open]: /help?cmd=open
294	196	[set]: /help?cmd=setting
295	197	[server]: /help?cmd=server
296	198	[stash]: /help?cmd=stash
297	199	[undo]: /help?cmd=undo
298	200

	--- www/gitusers.md
	+++ www/gitusers.md
	@@ -95,122 +95,25 @@
95
96	On a Windows box, you might instead choose "`C:\Fossils`"
97	and do without the subdirectory scheme, for example.
98
99
100	#### <a id="scw"></a> Single-Checkout Workflows
101
102	The most idiomatic way to use Fossil in the typical Git way — switching
103	between versions in a single check-out directory — is as follows:
104
105	fossil clone https://example.com/repo /path/to/repo.fossil
106	mkdir work-dir
107	cd work-dir
108	fossil open /path/to/repo.fossil
109	...work on trunk...
110	fossil update my-other-branch # like “git checkout”
111	...work on your other branch in the same directory...
112
113	In Fossil 2.12, we added a feature that allows you to get closer to
114	Git’s single-step clone-and-open behavior:
115
116	mkdir work-dir
117	cd work-dir
118	fossil open https://example.com/repo
119
120	Now you have “trunk” open in `work-dir`, with the repo file stored as
121	`repo.fossil` in that same directory.
122
123	The use of [`fossil open`][open] here instead of [`fossil clone`][clone]
124	likely surprises you as a Git user. When we were [discussing][caod]
125	this, we considered following the Git command style, but we decided
126	against it because it goes against this core Fossil design principle:
127	given that the Fossil repo is separate from the check-out, why would you
128	expect asking for a repo clone to also create a check-out directory for
129	you? We view commingled repository + check-out as a design error in
130	Git, so why would we repeat the error?
131
132	To see why we see this behavior is error-prone, consider that
133	`git clean` must have an exception to avoid nuking the `.git` directory.
134	We had to add that complication to `fossil clean` when we added the
135	`fossil open URI` feature: it won’t nuke the repo DB file.
136
137	This feature didn’t placate many Git fans, though, so with Fossil 2.14 —
138	currently unreleased — we now allow this:
139
140	fossil clone https://fossil-scm.org/fossil
141
142	This results in a `fossil.fossil` repo DB file and a `fossil/` working
143	directory.
144
145	Note that our `clone URI` behavior does not commingle the repo and
146	check-out, solving our major problem with the Git design, though we
147	still believe it to be confusing to have “clone” be part of “open,” and
148	still more confusing to have “open” part of “clone.” We prefer keeping
149	these operations entirely separate, either as at the [top of this
150	section](#scw) or [as in the next one](#mcw). Still, please yourself.
151
152	If you want the repo to be named something else, adjust the URL:
153
154	fossil clone https://fossil-scm.org/fossil/fsl
155
156	That gets you `fsl.fossil` checked out into `fsl/`.
157
158	For sites where the repo isn’t served from a subdirectory like this, you
159	might need another form of the URL. For example, you might have your
160	repo served from `dev.example.com` and want it cloned as `my-project`:
161
162	fossil clone https://dev.example.com/repo/my-project
163
164	The `/repo` addition is the key: whatever comes after is used as the
165	repository name. [See the docs][clone] for more details.
166
167	[caod]: https://fossil-scm.org/forum/forumpost/3f143cec74
168
169
170	#### <a id="mcw"></a> Multiple-Checkout Workflows
171
172	Because Fossil cleanly separates the repository from the check-out, it
173	is routine to have multiple check-outs from the same repository:
174
175	mkdir -p ~/src/my-project/trunk
176	cd ~/src/my-project/trunk
177	fossil open /path/to/repo.fossil # implicitly opens “trunk”
178	mkdir ../my-other-branch
179	cd ../my-other-branch
180	fossil open /path/to/repo.fossil my-other-branch
181	mkdir ../release
182	cd ../release
183	fossil open /path/to/repo.fossil release
184	mkdir ../scratch
185	cd ../scratch
186	fossil open /path/to/repo.fossil abcd1234
187	mkdir ../test
188	cd ../test
189	fossil open /path/to/repo.fossil 2019-04-01
190
191	Now you have five separate check-out directories: one each for trunk, an
192	alternate branch you’re working on, the latest tagged public release, a
193	“scratch” directory for experiments or brief bits of work you don’t want
194	to do in the other check-out directories, and a directory for testing a
195	user report of a bug in the trunk version as of last April Fool’s Day.
196	Each check-out operates independently of the others.
197
198	This multiple-checkouts working style is especially useful when Fossil stores source code in programming languages
199	where there is a “build” step that transforms source files into files
200	you actually run or distribute. With Git’s typical switch-in-place workflow,
201	you have to rebuild all outputs from the source files
202	that differ between those versions whenever you switch versions. In the above Fossil working model,
203	you switch versions with a “`cd`” command instead, so that you only have
204	to rebuild outputs from files you yourself change.
205
206	This style is also useful when a check-out directory may be tied up with
207	some long-running process, as with the “test” example above, where you
208	might need to run an hours-long brute-force replication script to tickle
209	a [Heisenbug][hb], forcing it to show itself. While that runs, you can
210	open a new terminal tab, “`cd ../trunk`”, and get back
211	to work.
212
213
214	#### <a id="close" name="dotfile"></a> Closing A Check-Out
215
216	The `fossil close` command dissaociates a check-out directory from the
	@@ -287,11 +190,10 @@
287
288
289	[clone]: /help?cmd=clone
290	[close]: /help?cmd=close
291	[gloss]: ./whyusefossil.wiki#definitions
292	[hb]: https://en.wikipedia.org/wiki/Heisenbug
293	[open]: /help?cmd=open
294	[set]: /help?cmd=setting
295	[server]: /help?cmd=server
296	[stash]: /help?cmd=stash
297	[undo]: /help?cmd=undo
298

	--- www/gitusers.md
	+++ www/gitusers.md
	@@ -95,122 +95,25 @@
95
96	On a Windows box, you might instead choose "`C:\Fossils`"
97	and do without the subdirectory scheme, for example.
98
99
100	#### <a id="cwork" name="scw"></a> Checkout Workflows
101
102	This is a complicated topic, so we [cover it elsewhere][cw].
103
104	The main Git-specific thing to add to that document is that this:
105
106	git checkout some-branch
107
108	…is spelled:
109
110	fossil update some-branch
111
112	…in Fossil.
113
114	[cw]: ./ckout-workflows.md

































































































115
116
117	#### <a id="close" name="dotfile"></a> Closing A Check-Out
118
119	The `fossil close` command dissaociates a check-out directory from the
	@@ -287,11 +190,10 @@
190
191
192	[clone]: /help?cmd=clone
193	[close]: /help?cmd=close
194	[gloss]: ./whyusefossil.wiki#definitions

195	[open]: /help?cmd=open
196	[set]: /help?cmd=setting
197	[server]: /help?cmd=server
198	[stash]: /help?cmd=stash
199	[undo]: /help?cmd=undo
200

M www/mkindex.tcl

		--- www/mkindex.tcl
		+++ www/mkindex.tcl
		@@ -27,10 +27,11 @@
27	27	cgi.wiki {CGI Script Configuration Options}
28	28	changes.wiki {Fossil Changelog}
29	29	checkin_names.wiki {Check-in And Version Names}
30	30	checkin.wiki {Check-in Checklist}
31	31	childprojects.wiki {Child Projects}
	32	+ ckout-workflows.md {Check-Out Workflows}
32	33	copyright-release.html {Contributor License Agreement}
33	34	concepts.wiki {Fossil Core Concepts}
34	35	contribute.wiki {Contributing Code or Documentation To The Fossil Project}
35	36	css-tricks.md {Fossil CSS Tips and Tricks}
36	37	customgraph.md {Theming: Customizing the Timeline Graph}
37	38

	--- www/mkindex.tcl
	+++ www/mkindex.tcl
	@@ -27,10 +27,11 @@
27	cgi.wiki {CGI Script Configuration Options}
28	changes.wiki {Fossil Changelog}
29	checkin_names.wiki {Check-in And Version Names}
30	checkin.wiki {Check-in Checklist}
31	childprojects.wiki {Child Projects}

32	copyright-release.html {Contributor License Agreement}
33	concepts.wiki {Fossil Core Concepts}
34	contribute.wiki {Contributing Code or Documentation To The Fossil Project}
35	css-tricks.md {Fossil CSS Tips and Tricks}
36	customgraph.md {Theming: Customizing the Timeline Graph}
37

	--- www/mkindex.tcl
	+++ www/mkindex.tcl
	@@ -27,10 +27,11 @@
27	cgi.wiki {CGI Script Configuration Options}
28	changes.wiki {Fossil Changelog}
29	checkin_names.wiki {Check-in And Version Names}
30	checkin.wiki {Check-in Checklist}
31	childprojects.wiki {Child Projects}
32	ckout-workflows.md {Check-Out Workflows}
33	copyright-release.html {Contributor License Agreement}
34	concepts.wiki {Fossil Core Concepts}
35	contribute.wiki {Contributing Code or Documentation To The Fossil Project}
36	css-tricks.md {Fossil CSS Tips and Tricks}
37	customgraph.md {Theming: Customizing the Timeline Graph}
38

M www/permutedindex.html

		--- www/permutedindex.html
		+++ www/permutedindex.html
		@@ -57,10 +57,11 @@
57	57	<li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li>
58	58	<li><a href="aboutcgi.wiki">CGI Works In Fossil — How</a></li>
59	59	<li><a href="changes.wiki">Changelog — Fossil</a></li>
60	60	<li><a href="checkin_names.wiki"><b>Check-in And Version Names</b></a></li>
61	61	<li><a href="checkin.wiki"><b>Check-in Checklist</b></a></li>
	62	+<li><a href="ckout-workflows.md"><b>Check-Out Workflows</b></a></li>
62	63	<li><a href="checkin.wiki">Checklist — Check-in</a></li>
63	64	<li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li>
64	65	<li><a href="foss-cklist.wiki"><b>Checklist For Successful Open-Source Projects</b></a></li>
65	66	<li><a href="selfcheck.wiki">Checks — Fossil Repository Integrity Self</a></li>
66	67	<li><a href="childprojects.wiki"><b>Child Projects</b></a></li>
		@@ -338,9 +339,10 @@
338	339	<li><a href="../../../help">Webpages — Lists of Commands and</a></li>
339	340	<li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li>
340	341	<li><a href="whyusefossil.wiki"><b>Why You Should Use Fossil</b></a></li>
341	342	<li><a href="../../../wiki_rules"><b>Wiki Formatting Rules</b></a></li>
342	343	<li><a href="wikitheory.wiki"><b>Wiki In Fossil</b></a></li>
	344	+<li><a href="ckout-workflows.md">Workflows — Check-Out</a></li>
343	345	<li><a href="aboutdownload.wiki">Works — How The Download Page</a></li>
344	346	<li><a href="aboutcgi.wiki">Works In Fossil — How CGI</a></li>
345	347	<li><a href="whyusefossil.wiki">You Should Use Fossil — Why</a></li>
346	348	</ul></div>
347	349

	--- www/permutedindex.html
	+++ www/permutedindex.html
	@@ -57,10 +57,11 @@
57	<li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li>
58	<li><a href="aboutcgi.wiki">CGI Works In Fossil — How</a></li>
59	<li><a href="changes.wiki">Changelog — Fossil</a></li>
60	<li><a href="checkin_names.wiki"><b>Check-in And Version Names</b></a></li>
61	<li><a href="checkin.wiki"><b>Check-in Checklist</b></a></li>

62	<li><a href="checkin.wiki">Checklist — Check-in</a></li>
63	<li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li>
64	<li><a href="foss-cklist.wiki"><b>Checklist For Successful Open-Source Projects</b></a></li>
65	<li><a href="selfcheck.wiki">Checks — Fossil Repository Integrity Self</a></li>
66	<li><a href="childprojects.wiki"><b>Child Projects</b></a></li>
	@@ -338,9 +339,10 @@
338	<li><a href="../../../help">Webpages — Lists of Commands and</a></li>
339	<li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li>
340	<li><a href="whyusefossil.wiki"><b>Why You Should Use Fossil</b></a></li>
341	<li><a href="../../../wiki_rules"><b>Wiki Formatting Rules</b></a></li>
342	<li><a href="wikitheory.wiki"><b>Wiki In Fossil</b></a></li>

343	<li><a href="aboutdownload.wiki">Works — How The Download Page</a></li>
344	<li><a href="aboutcgi.wiki">Works In Fossil — How CGI</a></li>
345	<li><a href="whyusefossil.wiki">You Should Use Fossil — Why</a></li>
346	</ul></div>
347

	--- www/permutedindex.html
	+++ www/permutedindex.html
	@@ -57,10 +57,11 @@
57	<li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li>
58	<li><a href="aboutcgi.wiki">CGI Works In Fossil — How</a></li>
59	<li><a href="changes.wiki">Changelog — Fossil</a></li>
60	<li><a href="checkin_names.wiki"><b>Check-in And Version Names</b></a></li>
61	<li><a href="checkin.wiki"><b>Check-in Checklist</b></a></li>
62	<li><a href="ckout-workflows.md"><b>Check-Out Workflows</b></a></li>
63	<li><a href="checkin.wiki">Checklist — Check-in</a></li>
64	<li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li>
65	<li><a href="foss-cklist.wiki"><b>Checklist For Successful Open-Source Projects</b></a></li>
66	<li><a href="selfcheck.wiki">Checks — Fossil Repository Integrity Self</a></li>
67	<li><a href="childprojects.wiki"><b>Child Projects</b></a></li>
	@@ -338,9 +339,10 @@
339	<li><a href="../../../help">Webpages — Lists of Commands and</a></li>
340	<li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li>
341	<li><a href="whyusefossil.wiki"><b>Why You Should Use Fossil</b></a></li>
342	<li><a href="../../../wiki_rules"><b>Wiki Formatting Rules</b></a></li>
343	<li><a href="wikitheory.wiki"><b>Wiki In Fossil</b></a></li>
344	<li><a href="ckout-workflows.md">Workflows — Check-Out</a></li>
345	<li><a href="aboutdownload.wiki">Works — How The Download Page</a></li>
346	<li><a href="aboutcgi.wiki">Works In Fossil — How CGI</a></li>
347	<li><a href="whyusefossil.wiki">You Should Use Fossil — Why</a></li>
348	</ul></div>
349

Fossil SCM

Keyboard Shortcuts