Fossil SCM

doc changes -- spelling corrections and embedded ref pages.

kejoki 2008-11-11 03:50 trunk
Commit 9eb6ea75c1aebbf2c25aaa5f58afac47d2a8b8df
Parent c66ffba6da9ed22…
11 files changed +4 -4 +3 -3 +37 +27 +5 -5 +2 -2 +2 -2 +1 -1 +8 -8 +3 -3 +629
~ www/bugtheory.wiki ~ www/build.wiki + www/cmd_extra.wiki + www/cmd_ls.wiki ~ www/concepts.wiki ~ www/delta_encoder_algorithm.wiki ~ www/delta_format.wiki ~ www/embeddeddoc.wiki ~ www/fileformat.wiki ~ www/index.wiki + www/reference.wiki
M www/bugtheory.wiki
+4 -4
--- www/bugtheory.wiki
+++ www/bugtheory.wiki
@@ -79,11 +79,11 @@
7979
 minutes or even a few hours. But if a timestamp on a ticket change
8080
 artifact is off by months or years, it can seriously confuse the
8181
 replay algorithm for determining the current ticket state. There
8282
 are techniques available to cause rogue artifacts to be ignored
8383
 by fossil. So if a ticket change artifact with a bad timestamp
84
-does get into a repository, it can be removed by an adminstrator.
84
+does get into a repository, it can be removed by an administrator.
8585
 But the best approach is to take steps to insure that timestamps
8686
 are approximately correct in the first place.
8787
8888
 <h2>Local Configuration</h2>
8989
@@ -102,20 +102,20 @@
102102
 algorithm, if a name/value pair is seen which has no corresponding column
103103
 in the TICKET table, then that name/value pair is ignored. Columns can
104104
 be added or removed from the TICKET table at any time. Whenever the
105105
 TICKET table is modified, the replay algorithm automatically reruns
106106
 to repopulate the table using the new column names. Note that the TICKET
107
-table schema and content is part of the local state of a respository
107
+table schema and content is part of the local state of a repository
108108
 and is not shared with other repositories during a sync, push, or pull.
109109
110110
 Each repository also defines scripts used to generate web pages for
111111
 creating new tickets, viewing existing tickets, and modifying an
112112
 existing ticket. These scripts consist of HTML with an embedded
113
-scripts written an a TCL-like language called "TH1". Every new fossil
113
+scripts written an a Tcl-like language called "TH1". Every new fossil
114114
 repository is created with default scripts. There is currently no
115
-documentation on the TH1 langauage. Administrators wishing to
115
+documentation on the TH1 language. Administrators wishing to
116116
 customize their ticket entry, viewing, and editing screens should
117117
 modify the default scripts to suit their needs. These screen generator
118118
 scripts are part of the local state of a repository and are not shared
119119
 with other repositories during a sync, push, or pull.
120120
121121
 <i>To be continued...</i>
122122
--- www/bugtheory.wiki
+++ www/bugtheory.wiki
@@ -79,11 +79,11 @@
79 minutes or even a few hours. But if a timestamp on a ticket change
80 artifact is off by months or years, it can seriously confuse the
81 replay algorithm for determining the current ticket state. There
82 are techniques available to cause rogue artifacts to be ignored
83 by fossil. So if a ticket change artifact with a bad timestamp
84 does get into a repository, it can be removed by an adminstrator.
85 But the best approach is to take steps to insure that timestamps
86 are approximately correct in the first place.
87
88 <h2>Local Configuration</h2>
89
@@ -102,20 +102,20 @@
102 algorithm, if a name/value pair is seen which has no corresponding column
103 in the TICKET table, then that name/value pair is ignored. Columns can
104 be added or removed from the TICKET table at any time. Whenever the
105 TICKET table is modified, the replay algorithm automatically reruns
106 to repopulate the table using the new column names. Note that the TICKET
107 table schema and content is part of the local state of a respository
108 and is not shared with other repositories during a sync, push, or pull.
109
110 Each repository also defines scripts used to generate web pages for
111 creating new tickets, viewing existing tickets, and modifying an
112 existing ticket. These scripts consist of HTML with an embedded
113 scripts written an a TCL-like language called "TH1". Every new fossil
114 repository is created with default scripts. There is currently no
115 documentation on the TH1 langauage. Administrators wishing to
116 customize their ticket entry, viewing, and editing screens should
117 modify the default scripts to suit their needs. These screen generator
118 scripts are part of the local state of a repository and are not shared
119 with other repositories during a sync, push, or pull.
120
121 <i>To be continued...</i>
122
--- www/bugtheory.wiki
+++ www/bugtheory.wiki
@@ -79,11 +79,11 @@
79 minutes or even a few hours. But if a timestamp on a ticket change
80 artifact is off by months or years, it can seriously confuse the
81 replay algorithm for determining the current ticket state. There
82 are techniques available to cause rogue artifacts to be ignored
83 by fossil. So if a ticket change artifact with a bad timestamp
84 does get into a repository, it can be removed by an administrator.
85 But the best approach is to take steps to insure that timestamps
86 are approximately correct in the first place.
87
88 <h2>Local Configuration</h2>
89
@@ -102,20 +102,20 @@
102 algorithm, if a name/value pair is seen which has no corresponding column
103 in the TICKET table, then that name/value pair is ignored. Columns can
104 be added or removed from the TICKET table at any time. Whenever the
105 TICKET table is modified, the replay algorithm automatically reruns
106 to repopulate the table using the new column names. Note that the TICKET
107 table schema and content is part of the local state of a repository
108 and is not shared with other repositories during a sync, push, or pull.
109
110 Each repository also defines scripts used to generate web pages for
111 creating new tickets, viewing existing tickets, and modifying an
112 existing ticket. These scripts consist of HTML with an embedded
113 scripts written an a Tcl-like language called "TH1". Every new fossil
114 repository is created with default scripts. There is currently no
115 documentation on the TH1 language. Administrators wishing to
116 customize their ticket entry, viewing, and editing screens should
117 modify the default scripts to suit their needs. These screen generator
118 scripts are part of the local state of a repository and are not shared
119 with other repositories during a sync, push, or pull.
120
121 <i>To be continued...</i>
122
M www/build.wiki
+3 -3
--- www/build.wiki
+++ www/build.wiki
@@ -2,15 +2,15 @@
22
 <h1>Installing Fossil</h1>
33
44
 <p>This page describes how to build and install Fossil. The
55
 whole process is designed to be very easy.</p>
66
7
-<h2>0.0 Using A Precompiled Binary</h2>
7
+<h2>0.0 Using A Pre-compiled Binary</h2>
88
99
 <p>You can skip steps 1.0 and 2.0 below by downloading
10
-a <a href="http://www.fossil-scm.org/download.html">precompiled binary</a>
11
-appropriate for your platform. If you use a precompiled binary
10
+a <a href="http://www.fossil-scm.org/download.html">pre-compiled binary</a>
11
+appropriate for your platform. If you use a pre-compiled binary
1212
 jump immediate to step 3.0.</p>
1313
1414
 <h2>1.0 Obtaining The Source Code</h2>
1515
1616
 <p>Fossil is self-hosting, so you can obtain a ZIP archive containing
1717
1818
ADDED www/cmd_extra.wiki
1919
ADDED www/cmd_ls.wiki
--- www/build.wiki
+++ www/build.wiki
@@ -2,15 +2,15 @@
2 <h1>Installing Fossil</h1>
3
4 <p>This page describes how to build and install Fossil. The
5 whole process is designed to be very easy.</p>
6
7 <h2>0.0 Using A Precompiled Binary</h2>
8
9 <p>You can skip steps 1.0 and 2.0 below by downloading
10 a <a href="http://www.fossil-scm.org/download.html">precompiled binary</a>
11 appropriate for your platform. If you use a precompiled binary
12 jump immediate to step 3.0.</p>
13
14 <h2>1.0 Obtaining The Source Code</h2>
15
16 <p>Fossil is self-hosting, so you can obtain a ZIP archive containing
17
18 DDED www/cmd_extra.wiki
19 DDED www/cmd_ls.wiki
--- www/build.wiki
+++ www/build.wiki
@@ -2,15 +2,15 @@
2 <h1>Installing Fossil</h1>
3
4 <p>This page describes how to build and install Fossil. The
5 whole process is designed to be very easy.</p>
6
7 <h2>0.0 Using A Pre-compiled Binary</h2>
8
9 <p>You can skip steps 1.0 and 2.0 below by downloading
10 a <a href="http://www.fossil-scm.org/download.html">pre-compiled binary</a>
11 appropriate for your platform. If you use a pre-compiled binary
12 jump immediate to step 3.0.</p>
13
14 <h2>1.0 Obtaining The Source Code</h2>
15
16 <p>Fossil is self-hosting, so you can obtain a ZIP archive containing
17
18 DDED www/cmd_extra.wiki
19 DDED www/cmd_ls.wiki
A www/cmd_extra.wiki
+37
--- a/www/cmd_extra.wiki
+++ b/www/cmd_extra.wiki
@@ -0,0 +1,37 @@
1
+<h2>extra</h2>
2
+
3
+The <code>extra</code> command is informational, it doesn't do anything to
4
+es are files that exist in a checked-out project, but it te
5
+
6
+Extra files are files that exist in a checked-out project, but don't belong to
7
+the repository.
8
+
9
+ belong to
10
+the repository.
11
+
12
+The <code>fossil extra</code> command will get
13
+
14
+This is convenient for fiadd</code>ed ein the repository before you
15
+tell yo
16
+u what e><a href="cmd_c.wiki | <codeclean</code> example, you have a "noo
17
+dle.src" file as a scratch pad
18
+for source code, and you d for source
19
+
20
+
21
+ode, and you don't epository? You don't <co
22
+repository? Yo ourse—though
23
+d
24
+
25
+tory? Yo ourse—though
26
+d
27
+it unintentionally. If yo r project is big, an
28
+d you want to
29
+find noodle.src, and anything else that isn't under source control with n the project
30
+directories, the
31
+
32
+
33
+If you don't think this is al you don't think th
34
+
35
+
36
+The <cod<h2>extra</h2>
37
+
--- a/www/cmd_extra.wiki
+++ b/www/cmd_extra.wiki
@@ -0,0 +1,37 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/cmd_extra.wiki
+++ b/www/cmd_extra.wiki
@@ -0,0 +1,37 @@
1 <h2>extra</h2>
2
3 The <code>extra</code> command is informational, it doesn't do anything to
4 es are files that exist in a checked-out project, but it te
5
6 Extra files are files that exist in a checked-out project, but don't belong to
7 the repository.
8
9 belong to
10 the repository.
11
12 The <code>fossil extra</code> command will get
13
14 This is convenient for fiadd</code>ed ein the repository before you
15 tell yo
16 u what e><a href="cmd_c.wiki | <codeclean</code> example, you have a "noo
17 dle.src" file as a scratch pad
18 for source code, and you d for source
19
20
21 ode, and you don't epository? You don't <co
22 repository? Yo ourse—though
23 d
24
25 tory? Yo ourse—though
26 d
27 it unintentionally. If yo r project is big, an
28 d you want to
29 find noodle.src, and anything else that isn't under source control with n the project
30 directories, the
31
32
33 If you don't think this is al you don't think th
34
35
36 The <cod<h2>extra</h2>
37
A www/cmd_ls.wiki
+27
--- a/www/cmd_ls.wiki
+++ b/www/cmd_ls.wiki
@@ -0,0 +1,27 @@
1
+<h2>ls</h2>
2
+
3
+The <code>ls</code><a href="#notes">*</a> command is informational, it doesn't do anything to
4
+, it doesn't do anything to
5
+a che
6
+
7
+ls you something about it.
8
+
9
+A project consists of a "source tree" ofdoc/tip/www/
10
+t this is a set of files and directories rooted
11
+at a main project director
12
+y. The files that are under source control aren't
13
+particularly distinguishab
14
+particularly distinguishable from those that aren't. The <code>ls</code> and
15
+
16
+
17
+<code>fossil ls</code> pr
18
+
19
+<code>fossil ls</code> produces a listing of the files which are under source
20
+control <i>and</i> their status within the repository. The output is a simple
21
+irs on separate [fossil add], [fossil rm], [fossiesn't do any<
22
+
23
+
24
+
25
+
26
+a <a href
27
+[Reference]
--- a/www/cmd_ls.wiki
+++ b/www/cmd_ls.wiki
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/cmd_ls.wiki
+++ b/www/cmd_ls.wiki
@@ -0,0 +1,27 @@
1 <h2>ls</h2>
2
3 The <code>ls</code><a href="#notes">*</a> command is informational, it doesn't do anything to
4 , it doesn't do anything to
5 a che
6
7 ls you something about it.
8
9 A project consists of a "source tree" ofdoc/tip/www/
10 t this is a set of files and directories rooted
11 at a main project director
12 y. The files that are under source control aren't
13 particularly distinguishab
14 particularly distinguishable from those that aren't. The <code>ls</code> and
15
16
17 <code>fossil ls</code> pr
18
19 <code>fossil ls</code> produces a listing of the files which are under source
20 control <i>and</i> their status within the repository. The output is a simple
21 irs on separate [fossil add], [fossil rm], [fossiesn't do any<
22
23
24
25
26 a <a href
27 [Reference]
M www/concepts.wiki
+5 -5
--- www/concepts.wiki
+++ www/concepts.wiki
@@ -73,11 +73,11 @@
7373
 except that instead of beginning with an existing local repository,
7474
 a clone begins with nothing and creates a new local repository that
7575
 is a duplicate of a remote repository.</p>
7676
7777
 <p>Communication between repositories is via HTTP. Remote
78
-repositories are identified by URL. You can also point a webbrowser
78
+repositories are identified by URL. You can also point a web browser
7979
 at a repository and get human-readable status, history, and tracking
8080
 information about the project.</p>
8181
8282
 <h3>2.1 Identification Of Artifacts</h3>
8383
@@ -85,11 +85,11 @@
8585
 Each artifact has a universally unique name which is the
8686
 <a href="http://en.wikipedia.org/wiki/SHA">SHA1</a> hash of the content
8787
 of that file expressed as 40 characters of lower-case hexadecimal. Such
8888
 a hash is referred to as the Artifact Identifier or Artifact ID
8989
 for the artifact. The SHA1 algorithm is created with the purpose of
90
-providing a highly forgery-resistent identifier for a file. Given any
90
+providing a highly forgery-resistant identifier for a file. Given any
9191
 file it is simple to find the artifact ID for that file. But given a
9292
 artifact ID it is computationally intractable to generate a file that will
9393
 have that Artifact ID.</p>
9494
9595
@@ -169,11 +169,11 @@
169169
 <h2>3.0 Fossil - The Program</h2>
170170
171171
 <p>Fossil is software. The implementation of fossil is in the form
172172
 of a single executable named "fossil". To install fossil on your system,
173173
 all you have to do is obtain a copy of this one executable file (either
174
-by downloading a precompiled version or compiling it yourself) and then
174
+by downloading a pre-compiled version or compiling it yourself) and then
175175
 putting that file somewhere on your PATH.</p>
176176
177177
 <p>Fossil is completely self-contained. It is not necessary to
178178
 install any other software in order to use fossil. You do <u>not</u> need
179179
 CVS, gzip, diff, rsync, Python, Perl, Tcl, Java, apache, PostgreSQL, MySQL,
@@ -370,11 +370,11 @@
370370
 <ol>
371371
 <li><p><b>Setting up a stand-alone server</b></p>
372372
373373
 <p>From within your source tree just use the <b>server</b> command and
374374
 fossil will start listening for incoming requests on TCP port 8080.
375
-You can point your webbrowser at <a href="http://localhost:8080/">
375
+You can point your web browser at <a href="http://localhost:8080/">
376376
 http://localhost:8080/</a> and begin exploring. Or your coworkers
377377
 can do pushes or pulls against your server. Use the <b>--port</b>
378378
 option to the server command to specify a different TCP port. If
379379
 you do not have a local source tree, use the <b>-R</b> command-line
380380
 option to specify the repository file.</p>
@@ -396,11 +396,11 @@
396396
 #!/usr/local/bin/fossil
397397
 repository: /home/me/bigproject.fossil
398398
 </pre></blockquote>
399399
400400
 <p>Edit this script to use whatever pathnames are appropriate for
401
-your project. Then point your webbrowser at the script and off you
401
+your project. Then point your web browser at the script and off you
402402
 go.</p></li>
403403
404404
 <li><p><b>Setting up an inetd server</b></p>
405405
406406
 <p>If you have inetd or xinetd running on your system, you can set
407407
--- www/concepts.wiki
+++ www/concepts.wiki
@@ -73,11 +73,11 @@
73 except that instead of beginning with an existing local repository,
74 a clone begins with nothing and creates a new local repository that
75 is a duplicate of a remote repository.</p>
76
77 <p>Communication between repositories is via HTTP. Remote
78 repositories are identified by URL. You can also point a webbrowser
79 at a repository and get human-readable status, history, and tracking
80 information about the project.</p>
81
82 <h3>2.1 Identification Of Artifacts</h3>
83
@@ -85,11 +85,11 @@
85 Each artifact has a universally unique name which is the
86 <a href="http://en.wikipedia.org/wiki/SHA">SHA1</a> hash of the content
87 of that file expressed as 40 characters of lower-case hexadecimal. Such
88 a hash is referred to as the Artifact Identifier or Artifact ID
89 for the artifact. The SHA1 algorithm is created with the purpose of
90 providing a highly forgery-resistent identifier for a file. Given any
91 file it is simple to find the artifact ID for that file. But given a
92 artifact ID it is computationally intractable to generate a file that will
93 have that Artifact ID.</p>
94
95
@@ -169,11 +169,11 @@
169 <h2>3.0 Fossil - The Program</h2>
170
171 <p>Fossil is software. The implementation of fossil is in the form
172 of a single executable named "fossil". To install fossil on your system,
173 all you have to do is obtain a copy of this one executable file (either
174 by downloading a precompiled version or compiling it yourself) and then
175 putting that file somewhere on your PATH.</p>
176
177 <p>Fossil is completely self-contained. It is not necessary to
178 install any other software in order to use fossil. You do <u>not</u> need
179 CVS, gzip, diff, rsync, Python, Perl, Tcl, Java, apache, PostgreSQL, MySQL,
@@ -370,11 +370,11 @@
370 <ol>
371 <li><p><b>Setting up a stand-alone server</b></p>
372
373 <p>From within your source tree just use the <b>server</b> command and
374 fossil will start listening for incoming requests on TCP port 8080.
375 You can point your webbrowser at <a href="http://localhost:8080/">
376 http://localhost:8080/</a> and begin exploring. Or your coworkers
377 can do pushes or pulls against your server. Use the <b>--port</b>
378 option to the server command to specify a different TCP port. If
379 you do not have a local source tree, use the <b>-R</b> command-line
380 option to specify the repository file.</p>
@@ -396,11 +396,11 @@
396 #!/usr/local/bin/fossil
397 repository: /home/me/bigproject.fossil
398 </pre></blockquote>
399
400 <p>Edit this script to use whatever pathnames are appropriate for
401 your project. Then point your webbrowser at the script and off you
402 go.</p></li>
403
404 <li><p><b>Setting up an inetd server</b></p>
405
406 <p>If you have inetd or xinetd running on your system, you can set
407
--- www/concepts.wiki
+++ www/concepts.wiki
@@ -73,11 +73,11 @@
73 except that instead of beginning with an existing local repository,
74 a clone begins with nothing and creates a new local repository that
75 is a duplicate of a remote repository.</p>
76
77 <p>Communication between repositories is via HTTP. Remote
78 repositories are identified by URL. You can also point a web browser
79 at a repository and get human-readable status, history, and tracking
80 information about the project.</p>
81
82 <h3>2.1 Identification Of Artifacts</h3>
83
@@ -85,11 +85,11 @@
85 Each artifact has a universally unique name which is the
86 <a href="http://en.wikipedia.org/wiki/SHA">SHA1</a> hash of the content
87 of that file expressed as 40 characters of lower-case hexadecimal. Such
88 a hash is referred to as the Artifact Identifier or Artifact ID
89 for the artifact. The SHA1 algorithm is created with the purpose of
90 providing a highly forgery-resistant identifier for a file. Given any
91 file it is simple to find the artifact ID for that file. But given a
92 artifact ID it is computationally intractable to generate a file that will
93 have that Artifact ID.</p>
94
95
@@ -169,11 +169,11 @@
169 <h2>3.0 Fossil - The Program</h2>
170
171 <p>Fossil is software. The implementation of fossil is in the form
172 of a single executable named "fossil". To install fossil on your system,
173 all you have to do is obtain a copy of this one executable file (either
174 by downloading a pre-compiled version or compiling it yourself) and then
175 putting that file somewhere on your PATH.</p>
176
177 <p>Fossil is completely self-contained. It is not necessary to
178 install any other software in order to use fossil. You do <u>not</u> need
179 CVS, gzip, diff, rsync, Python, Perl, Tcl, Java, apache, PostgreSQL, MySQL,
@@ -370,11 +370,11 @@
370 <ol>
371 <li><p><b>Setting up a stand-alone server</b></p>
372
373 <p>From within your source tree just use the <b>server</b> command and
374 fossil will start listening for incoming requests on TCP port 8080.
375 You can point your web browser at <a href="http://localhost:8080/">
376 http://localhost:8080/</a> and begin exploring. Or your coworkers
377 can do pushes or pulls against your server. Use the <b>--port</b>
378 option to the server command to specify a different TCP port. If
379 you do not have a local source tree, use the <b>-R</b> command-line
380 option to specify the repository file.</p>
@@ -396,11 +396,11 @@
396 #!/usr/local/bin/fossil
397 repository: /home/me/bigproject.fossil
398 </pre></blockquote>
399
400 <p>Edit this script to use whatever pathnames are appropriate for
401 your project. Then point your web browser at the script and off you
402 go.</p></li>
403
404 <li><p><b>Setting up an inetd server</b></p>
405
406 <p>If you have inetd or xinetd running on your system, you can set
407
M www/delta_encoder_algorithm.wiki
+2 -2
--- www/delta_encoder_algorithm.wiki
+++ www/delta_encoder_algorithm.wiki
@@ -79,11 +79,11 @@
7979
 ignored.
8080
 </li>
8181
 <li>The <a href="#rollhash">rolling hash</a> of each chunk is
8282
 computed.
8383
 </li>
84
-<li>A hashtable is filled, mapping from the hashes of the chunks to
84
+<li>A hash table is filled, mapping from the hashes of the chunks to
8585
 the list of chunk locations having this hash.
8686
 </li>
8787
 </ol>
8888
8989
 <a name="processing"></a><h3>2.1 Processing the target</h3>
@@ -112,11 +112,11 @@
112112
113113
 <img src="encode10.gif" align="right" hspace="10">
114114
 <p>To make this decision the encoder first computes the hash value for
115115
 the NHASH bytes in the window and then looks at all the locations in
116116
 the "origin" which have the same signature. This part uses the hash
117
-table created by the pre-processing step to effiently find these
117
+table created by the pre-processing step to efficiently find these
118118
 locations.</p>
119119
120120
 <p>For each of the possible candidates the encoder finds the maximal
121121
 range of bytes common to both "origin" and "target", going forward and
122122
 backward from "slide" in the "target", and the candidate location in
123123
--- www/delta_encoder_algorithm.wiki
+++ www/delta_encoder_algorithm.wiki
@@ -79,11 +79,11 @@
79 ignored.
80 </li>
81 <li>The <a href="#rollhash">rolling hash</a> of each chunk is
82 computed.
83 </li>
84 <li>A hashtable is filled, mapping from the hashes of the chunks to
85 the list of chunk locations having this hash.
86 </li>
87 </ol>
88
89 <a name="processing"></a><h3>2.1 Processing the target</h3>
@@ -112,11 +112,11 @@
112
113 <img src="encode10.gif" align="right" hspace="10">
114 <p>To make this decision the encoder first computes the hash value for
115 the NHASH bytes in the window and then looks at all the locations in
116 the "origin" which have the same signature. This part uses the hash
117 table created by the pre-processing step to effiently find these
118 locations.</p>
119
120 <p>For each of the possible candidates the encoder finds the maximal
121 range of bytes common to both "origin" and "target", going forward and
122 backward from "slide" in the "target", and the candidate location in
123
--- www/delta_encoder_algorithm.wiki
+++ www/delta_encoder_algorithm.wiki
@@ -79,11 +79,11 @@
79 ignored.
80 </li>
81 <li>The <a href="#rollhash">rolling hash</a> of each chunk is
82 computed.
83 </li>
84 <li>A hash table is filled, mapping from the hashes of the chunks to
85 the list of chunk locations having this hash.
86 </li>
87 </ol>
88
89 <a name="processing"></a><h3>2.1 Processing the target</h3>
@@ -112,11 +112,11 @@
112
113 <img src="encode10.gif" align="right" hspace="10">
114 <p>To make this decision the encoder first computes the hash value for
115 the NHASH bytes in the window and then looks at all the locations in
116 the "origin" which have the same signature. This part uses the hash
117 table created by the pre-processing step to efficiently find these
118 locations.</p>
119
120 <p>For each of the possible candidates the encoder finds the maximal
121 range of bytes common to both "origin" and "target", going forward and
122 backward from "slide" in the "target", and the candidate location in
123
M www/delta_format.wiki
+2 -2
--- www/delta_format.wiki
+++ www/delta_format.wiki
@@ -178,12 +178,12 @@
178178
179179
 @@ -27,8 +27,8 @@
180180
 * Additional information displayed for the "vinfo" page:
181181
182182
 + All leaves of this version that are not included in the
183
-- decendant list. With date, user, comment, and hyperlink.
184
-- Leaves in the decendant table should be marked as such.
183
+- descendant list. With date, user, comment, and hyperlink.
184
+- Leaves in the descendant table should be marked as such.
185185
 + descendant list. With date, user, comment, and hyperlink.
186186
 + Leaves in the descendant table should be marked as such.
187187
 See the compute_leaves() function to see how to find all
188188
 leaves.
189189
 + Add file diff links to the file change list.
190190
--- www/delta_format.wiki
+++ www/delta_format.wiki
@@ -178,12 +178,12 @@
178
179 @@ -27,8 +27,8 @@
180 * Additional information displayed for the "vinfo" page:
181
182 + All leaves of this version that are not included in the
183 - decendant list. With date, user, comment, and hyperlink.
184 - Leaves in the decendant table should be marked as such.
185 + descendant list. With date, user, comment, and hyperlink.
186 + Leaves in the descendant table should be marked as such.
187 See the compute_leaves() function to see how to find all
188 leaves.
189 + Add file diff links to the file change list.
190
--- www/delta_format.wiki
+++ www/delta_format.wiki
@@ -178,12 +178,12 @@
178
179 @@ -27,8 +27,8 @@
180 * Additional information displayed for the "vinfo" page:
181
182 + All leaves of this version that are not included in the
183 - descendant list. With date, user, comment, and hyperlink.
184 - Leaves in the descendant table should be marked as such.
185 + descendant list. With date, user, comment, and hyperlink.
186 + Leaves in the descendant table should be marked as such.
187 See the compute_leaves() function to see how to find all
188 leaves.
189 + Add file diff links to the file change list.
190
M www/embeddeddoc.wiki
+1 -1
--- www/embeddeddoc.wiki
+++ www/embeddeddoc.wiki
@@ -51,11 +51,11 @@
5151
 version of the documentation. The "<b>ckout</b>" keywords means to
5252
 pull the documentation file from the local source tree on disk, not
5353
 from the any versioned baseline. The "<b>ckout</b>" keyword normally
5454
 only works when you start your server using the "<b>fossil server</b>"
5555
 or "<b>fossil ui</b>"
56
-command line and is intented to show what the documentation you are currently
56
+command line and is indented to show what the documentation you are currently
5757
 editing looks like before you check it in.
5858
5959
 Finally, the <i>&lt;filename&gt;</i> element of the URL is the full
6060
 pathname of the documentation file starting from the root of the source
6161
 tree.
6262
--- www/embeddeddoc.wiki
+++ www/embeddeddoc.wiki
@@ -51,11 +51,11 @@
51 version of the documentation. The "<b>ckout</b>" keywords means to
52 pull the documentation file from the local source tree on disk, not
53 from the any versioned baseline. The "<b>ckout</b>" keyword normally
54 only works when you start your server using the "<b>fossil server</b>"
55 or "<b>fossil ui</b>"
56 command line and is intented to show what the documentation you are currently
57 editing looks like before you check it in.
58
59 Finally, the <i>&lt;filename&gt;</i> element of the URL is the full
60 pathname of the documentation file starting from the root of the source
61 tree.
62
--- www/embeddeddoc.wiki
+++ www/embeddeddoc.wiki
@@ -51,11 +51,11 @@
51 version of the documentation. The "<b>ckout</b>" keywords means to
52 pull the documentation file from the local source tree on disk, not
53 from the any versioned baseline. The "<b>ckout</b>" keyword normally
54 only works when you start your server using the "<b>fossil server</b>"
55 or "<b>fossil ui</b>"
56 command line and is indented to show what the documentation you are currently
57 editing looks like before you check it in.
58
59 Finally, the <i>&lt;filename&gt;</i> element of the URL is the full
60 pathname of the documentation file starting from the root of the source
61 tree.
62
M www/fileformat.wiki
+8 -8
--- www/fileformat.wiki
+++ www/fileformat.wiki
@@ -139,11 +139,11 @@
139139
140140
 <p>
141141
 A manifest has zero or more F-cards. Each F-card defines a file
142142
 (other than the manifest itself) which is part of the baseline that
143143
 the manifest defines. There are two, three, or three arguments.
144
-The first argment
144
+The first argument
145145
 is the pathname of the file in the baseline relative to the root
146146
 of the project file hierarchy. No ".." or "." directories are allowed
147147
 within the filename. Space characters are escaped as in C-card
148148
 comment text. Backslash characters and newlines are not allowed
149149
 within filenames. The directory separator character is a forward
@@ -203,19 +203,19 @@
203203
204204
 <p>
205205
 A manifest has an option Z-card as its last line. The argument
206206
 to the Z-card is a 32-character lowercase hexadecimal MD5 hash
207207
 of all prior lines of the manifest up to and including the newline
208
-character that immediately preceeds the "Z". The Z-card is just
208
+character that immediately precedes the "Z". The Z-card is just
209209
 a sanity check to prove that the manifest is well-formed and
210210
 consistent.
211211
 </p>
212212
213213
 <h2>2.0 Clusters</h2>
214214
215215
 <p>
216
-A cluster is a artifact that declares the existance of other artifacts.
216
+A cluster is a artifact that declares the existence of other artifacts.
217217
 Clusters are used during repository synchronization to help
218218
 reduce network traffic. As such, clusters are an optimization and
219219
 may be removed from a repository without loss or damage to the
220220
 underlying project code.
221221
 </p>
@@ -228,11 +228,11 @@
228228
 the card type. All arguments are separated from each other
229229
 and from the card-type character by a single space
230230
 character. There is no surplus white space between arguments
231231
 and no leading or trailing whitespace except for the newline
232232
 character that acts as the card separator.
233
-All cards of a cluter occur in strict sorted lexicographical order.
233
+All cards of a cluster occur in strict sorted lexicographical order.
234234
 No card may be duplicated.
235235
 The cluster may not contain additional text or data beyond
236236
 what is described here.
237237
 Unlike manifests, clusters are never PGP signed.
238238
 </p>
@@ -294,12 +294,12 @@
294294
 to which the tag is to be applied. The
295295
 first value is the tag name. The first character of the tag
296296
 is either "+", "-", or "*". A "+" means the tag should be added
297297
 to the artifact. The "-" means the tag should be removed.
298298
 The "*" character means the tag should be added to the artifact
299
-and all direct decendants (but not branches) of the artifact down
300
-to but not including the first decendant that contains a
299
+and all direct descendants (but not branches) of the artifact down
300
+to but not including the first descendant that contains a
301301
 more recent "-" tag with the same name.
302302
 The optional third argument is the value of the tag. A tag
303303
 without a value is a boolean.</p>
304304
305305
 <p>When two or more tags with the same name are applied to the
@@ -362,20 +362,20 @@
362362
363363
 <p>
364364
 Every ticket has a unique ID. The ticket to which this change is applied
365365
 is specified by the K card. A ticket exists if it contains one or
366366
 more changes. The first "change" to a ticket is what brings the
367
-ticket into existance.</p>
367
+ticket into existence.</p>
368368
369369
 <p>
370370
 J cards specify changes to the "value" of "fields" in the ticket.
371371
 If the <i>value</i> parameter of the J card is omitted, then the
372372
 field is set to an empty string.
373373
 Each fossil server has a ticket configuration which specifies the fields its
374374
 understands. The ticket configuration is part of the local state for
375375
 the repository and thus can vary from one repository to another.
376
-Hencd a J card might specify a <i>field</i> that do not exist in the
376
+Hence a J card might specify a <i>field</i> that do not exist in the
377377
 local ticket configuration. If a J card specifies a <i>field</i> that
378378
 is not in the local configuration, then that J card
379379
 is simply ignored.</p>
380380
381381
 <p>
382382
--- www/fileformat.wiki
+++ www/fileformat.wiki
@@ -139,11 +139,11 @@
139
140 <p>
141 A manifest has zero or more F-cards. Each F-card defines a file
142 (other than the manifest itself) which is part of the baseline that
143 the manifest defines. There are two, three, or three arguments.
144 The first argment
145 is the pathname of the file in the baseline relative to the root
146 of the project file hierarchy. No ".." or "." directories are allowed
147 within the filename. Space characters are escaped as in C-card
148 comment text. Backslash characters and newlines are not allowed
149 within filenames. The directory separator character is a forward
@@ -203,19 +203,19 @@
203
204 <p>
205 A manifest has an option Z-card as its last line. The argument
206 to the Z-card is a 32-character lowercase hexadecimal MD5 hash
207 of all prior lines of the manifest up to and including the newline
208 character that immediately preceeds the "Z". The Z-card is just
209 a sanity check to prove that the manifest is well-formed and
210 consistent.
211 </p>
212
213 <h2>2.0 Clusters</h2>
214
215 <p>
216 A cluster is a artifact that declares the existance of other artifacts.
217 Clusters are used during repository synchronization to help
218 reduce network traffic. As such, clusters are an optimization and
219 may be removed from a repository without loss or damage to the
220 underlying project code.
221 </p>
@@ -228,11 +228,11 @@
228 the card type. All arguments are separated from each other
229 and from the card-type character by a single space
230 character. There is no surplus white space between arguments
231 and no leading or trailing whitespace except for the newline
232 character that acts as the card separator.
233 All cards of a cluter occur in strict sorted lexicographical order.
234 No card may be duplicated.
235 The cluster may not contain additional text or data beyond
236 what is described here.
237 Unlike manifests, clusters are never PGP signed.
238 </p>
@@ -294,12 +294,12 @@
294 to which the tag is to be applied. The
295 first value is the tag name. The first character of the tag
296 is either "+", "-", or "*". A "+" means the tag should be added
297 to the artifact. The "-" means the tag should be removed.
298 The "*" character means the tag should be added to the artifact
299 and all direct decendants (but not branches) of the artifact down
300 to but not including the first decendant that contains a
301 more recent "-" tag with the same name.
302 The optional third argument is the value of the tag. A tag
303 without a value is a boolean.</p>
304
305 <p>When two or more tags with the same name are applied to the
@@ -362,20 +362,20 @@
362
363 <p>
364 Every ticket has a unique ID. The ticket to which this change is applied
365 is specified by the K card. A ticket exists if it contains one or
366 more changes. The first "change" to a ticket is what brings the
367 ticket into existance.</p>
368
369 <p>
370 J cards specify changes to the "value" of "fields" in the ticket.
371 If the <i>value</i> parameter of the J card is omitted, then the
372 field is set to an empty string.
373 Each fossil server has a ticket configuration which specifies the fields its
374 understands. The ticket configuration is part of the local state for
375 the repository and thus can vary from one repository to another.
376 Hencd a J card might specify a <i>field</i> that do not exist in the
377 local ticket configuration. If a J card specifies a <i>field</i> that
378 is not in the local configuration, then that J card
379 is simply ignored.</p>
380
381 <p>
382
--- www/fileformat.wiki
+++ www/fileformat.wiki
@@ -139,11 +139,11 @@
139
140 <p>
141 A manifest has zero or more F-cards. Each F-card defines a file
142 (other than the manifest itself) which is part of the baseline that
143 the manifest defines. There are two, three, or three arguments.
144 The first argument
145 is the pathname of the file in the baseline relative to the root
146 of the project file hierarchy. No ".." or "." directories are allowed
147 within the filename. Space characters are escaped as in C-card
148 comment text. Backslash characters and newlines are not allowed
149 within filenames. The directory separator character is a forward
@@ -203,19 +203,19 @@
203
204 <p>
205 A manifest has an option Z-card as its last line. The argument
206 to the Z-card is a 32-character lowercase hexadecimal MD5 hash
207 of all prior lines of the manifest up to and including the newline
208 character that immediately precedes the "Z". The Z-card is just
209 a sanity check to prove that the manifest is well-formed and
210 consistent.
211 </p>
212
213 <h2>2.0 Clusters</h2>
214
215 <p>
216 A cluster is a artifact that declares the existence of other artifacts.
217 Clusters are used during repository synchronization to help
218 reduce network traffic. As such, clusters are an optimization and
219 may be removed from a repository without loss or damage to the
220 underlying project code.
221 </p>
@@ -228,11 +228,11 @@
228 the card type. All arguments are separated from each other
229 and from the card-type character by a single space
230 character. There is no surplus white space between arguments
231 and no leading or trailing whitespace except for the newline
232 character that acts as the card separator.
233 All cards of a cluster occur in strict sorted lexicographical order.
234 No card may be duplicated.
235 The cluster may not contain additional text or data beyond
236 what is described here.
237 Unlike manifests, clusters are never PGP signed.
238 </p>
@@ -294,12 +294,12 @@
294 to which the tag is to be applied. The
295 first value is the tag name. The first character of the tag
296 is either "+", "-", or "*". A "+" means the tag should be added
297 to the artifact. The "-" means the tag should be removed.
298 The "*" character means the tag should be added to the artifact
299 and all direct descendants (but not branches) of the artifact down
300 to but not including the first descendant that contains a
301 more recent "-" tag with the same name.
302 The optional third argument is the value of the tag. A tag
303 without a value is a boolean.</p>
304
305 <p>When two or more tags with the same name are applied to the
@@ -362,20 +362,20 @@
362
363 <p>
364 Every ticket has a unique ID. The ticket to which this change is applied
365 is specified by the K card. A ticket exists if it contains one or
366 more changes. The first "change" to a ticket is what brings the
367 ticket into existence.</p>
368
369 <p>
370 J cards specify changes to the "value" of "fields" in the ticket.
371 If the <i>value</i> parameter of the J card is omitted, then the
372 field is set to an empty string.
373 Each fossil server has a ticket configuration which specifies the fields its
374 understands. The ticket configuration is part of the local state for
375 the repository and thus can vary from one repository to another.
376 Hence a J card might specify a <i>field</i> that do not exist in the
377 local ticket configuration. If a J card specifies a <i>field</i> that
378 is not in the local configuration, then that J card
379 is simply ignored.</p>
380
381 <p>
382
M www/index.wiki
+3 -3
--- www/index.wiki
+++ www/index.wiki
@@ -9,14 +9,14 @@
99
 easy-to-use, stand-alone executable.
1010
 Fossil is
1111
 <a href="http://www.fossil-scm.org/">self-hosting</a>
1212
 since 2007-07-21 on
1313
 <a href="http://www.hwaci.com/cgi-bin/fossil">two separate servers</a>.
14
-You can download the <a href="../../../timeline">lastest sources</a> and
14
+You can download the <a href="../../../timeline">latest sources</a> and
1515
 <a href="build.wiki">compile it yourself</a>.
1616
 Or you can grab
17
-<a href="http://www.fossil-scm.org/download.html">precompiled binaries</a>.
17
+<a href="http://www.fossil-scm.org/download.html">pre-compiled binaries</a>.
1818
 </p>
1919
2020
 <p>Feature Summary:</p>
2121
2222
 <ul>
@@ -42,11 +42,11 @@
4242
 <li>Everything (client, server, and utilities) is included in a
4343
 single self-contained executable - trivial to install</li>
4444
 <li>Server runs as <a href="quickstart.wiki#cgiserver">CGI</a>, using
4545
 <a href="quickstart.wiki#inetdserver">inetd/xinetd</a>
4646
 or using its own
47
-<a href="quickstart.wiki#serversetup">built-in, standalone web server</a>.</li>
47
+<a href="quickstart.wiki#serversetup">built-in, stand alone web server</a>.</li>
4848
 <li>An entire project contained in single disk file
4949
 (an <a href="http://www.sqlite.org/">SQLite</a> database.)</li>
5050
 <li>Uses an <a href="fileformat.wiki">enduring file format</a> that is
5151
 designed to be readable, searchable, and extensible by people not yet born.</li>
5252
 <li>Automatic <a href="selfcheck.wiki">self-check</a>
5353
5454
ADDED www/reference.wiki
--- www/index.wiki
+++ www/index.wiki
@@ -9,14 +9,14 @@
9 easy-to-use, stand-alone executable.
10 Fossil is
11 <a href="http://www.fossil-scm.org/">self-hosting</a>
12 since 2007-07-21 on
13 <a href="http://www.hwaci.com/cgi-bin/fossil">two separate servers</a>.
14 You can download the <a href="../../../timeline">lastest sources</a> and
15 <a href="build.wiki">compile it yourself</a>.
16 Or you can grab
17 <a href="http://www.fossil-scm.org/download.html">precompiled binaries</a>.
18 </p>
19
20 <p>Feature Summary:</p>
21
22 <ul>
@@ -42,11 +42,11 @@
42 <li>Everything (client, server, and utilities) is included in a
43 single self-contained executable - trivial to install</li>
44 <li>Server runs as <a href="quickstart.wiki#cgiserver">CGI</a>, using
45 <a href="quickstart.wiki#inetdserver">inetd/xinetd</a>
46 or using its own
47 <a href="quickstart.wiki#serversetup">built-in, standalone web server</a>.</li>
48 <li>An entire project contained in single disk file
49 (an <a href="http://www.sqlite.org/">SQLite</a> database.)</li>
50 <li>Uses an <a href="fileformat.wiki">enduring file format</a> that is
51 designed to be readable, searchable, and extensible by people not yet born.</li>
52 <li>Automatic <a href="selfcheck.wiki">self-check</a>
53
54 DDED www/reference.wiki
--- www/index.wiki
+++ www/index.wiki
@@ -9,14 +9,14 @@
9 easy-to-use, stand-alone executable.
10 Fossil is
11 <a href="http://www.fossil-scm.org/">self-hosting</a>
12 since 2007-07-21 on
13 <a href="http://www.hwaci.com/cgi-bin/fossil">two separate servers</a>.
14 You can download the <a href="../../../timeline">latest sources</a> and
15 <a href="build.wiki">compile it yourself</a>.
16 Or you can grab
17 <a href="http://www.fossil-scm.org/download.html">pre-compiled binaries</a>.
18 </p>
19
20 <p>Feature Summary:</p>
21
22 <ul>
@@ -42,11 +42,11 @@
42 <li>Everything (client, server, and utilities) is included in a
43 single self-contained executable - trivial to install</li>
44 <li>Server runs as <a href="quickstart.wiki#cgiserver">CGI</a>, using
45 <a href="quickstart.wiki#inetdserver">inetd/xinetd</a>
46 or using its own
47 <a href="quickstart.wiki#serversetup">built-in, stand alone web server</a>.</li>
48 <li>An entire project contained in single disk file
49 (an <a href="http://www.sqlite.org/">SQLite</a> database.)</li>
50 <li>Uses an <a href="fileformat.wiki">enduring file format</a> that is
51 designed to be readable, searchable, and extensible by people not yet born.</li>
52 <li>Automatic <a href="selfcheck.wiki">self-check</a>
53
54 DDED www/reference.wiki
A www/reference.wiki
+629
--- a/www/reference.wiki
+++ b/www/reference.wiki
@@ -0,0 +1,629 @@
1
+ of fossil as
2
+
3
+The <code>fossil</code> program supplies most of the actual
4
+documentation about its options, so a good way to start documenting
5
+the program is to nab the output of <code>fossil help <i>command</i></code>
6
+for all of its (exposed) cli.
7
+
8
+<i>This was suggested under the <b>Reference</b> heading in
9
+[Documentation outline].
10
+
11
+SCM) systems—but not <i>too</i>
12
+ much.
13
+
14
+ If you are trying to (cl
15
+
16
+rmation about fodoc/tip/www/ssil'
17
+ are trying to (cli)fossil as a shell you invnk orm">rmcl.
18
+ Think of fo
19
+">rmcl.
20
+ Think of fossil as i>distinct</i> prefix of A40 characte
21
+ssil as a shell you invoke and feed a command to,
22
+ including any optionsnkeffectivel looking for that string | clone the repository formbthe repos
23
+ry f </tr>
24
+
25
+(Sut not <i>too</i>
26
+ much.
27
+
28
+ I
29
+href="widel not <i>to2;aintenence (Smerge">mergeil Home</a> and
30
+ <a
31
+ersion</u>]
32
+ in <b>fossil</b> is a 40-character loanges">changesa
33
+enough(Smerge">mergeil Homals web
34
+ capabil
35
+
36
+iki">Fossil Home</a> and
37
+ <a href="wie special delimiteat string | c
38
+e>diff not <i>to2;aintenence
39
+
40
+f not <i>to2
41
+akethe-e�but not <i>too<n
42
+
43
+Available COMMANDs:
44
+add configuration leaves redo ui
45
+all deconstruct ls rename undo
46
+cgi del merge revert unset
47
+changes descendants mv rm update
48
+checkout diff new server user
49
+ci extra openl as a s settings version
50
+clean gdiff pull status wiki
51
+clone help push sync
52
+close http rebuild tag
53
+commit info not <i </pre></nowiki>
54
+ nten
55
+</pre></nowiki>
56
+nc of A40 c haracter hexadecimal string.
57
+ibu d environment c
58
+ching.wiki | explanat that is d
59
+fossil</b <tr>
60
+ ersion yommands do not use speconcepts.wiki#ke y
61
+c | <u>versi <nowiki><pre>
62
+
63
+ -character longts.wiki#knk of fossil as a s
64
+iki#knk of foss
65
+<nowiki><pre>
66
+
67
+Usage: </nowiki><code>[fossil add]</code><nowiki> FILE...
68
+
69
+l makethe-e�but not <i>too<n
70
+ entered to make the intent unambigu
71
+nk of fossil as a snvoke and feed a command to </nowiki><code>[fossil all]</code><nowikiV@11E,B:
72
+
73
+The ~/.7@D~,C:file recordsX@15z,8: for a
74
+13@12u,2:
75
+17@141,2:
76
+P@15D,4:
77
+
78
+r@15e,4:
79
+
80
+t@16Y,4:
81
+
82
+j@17T,4:
83
+
84
+e@18E,4:
85
+
86
+j@18v,4:
87
+
88
+16@19j,2:
89
+17@1Au,1A:
90
+pull, push, or sync
91
+
92
+
93
+Usage: </nowiki>[fossil cgi]<nowiki> SCRIPT
94
+
95
+10@1Dl,2:
96
+z@1Eq,2:
97
+11@1Ft,2:
98
+13@1Gz,2:
99
+h@1I6,T:
100
+
101
+ #!/usr/bin/fossil
102
+ e@1JA,4:
103
+
104
+13@1Ju,2:
105
+11@1L1,2:
106
+m@1M7,n:
107
+
108
+
109
+Usage: </nowiki>[fossil changes]<nowiki>
110
+
111
+~@1OL,2:
112
+g@1PP,j:
113
+
114
+
115
+Usage: </nowiki>[fossil checkout]<nowikiM@1RD,4:
116
+
117
+10@1Re,2:
118
+z@1Sj,2:
119
+k@1Tm,4:
120
+
121
+U@1Ub,h:
122
+
123
+
124
+Usage: </nowiki>[fossil commit]<nowikiZ@1WS,5:
125
+ U@1X0,4:
126
+
127
+11@1X_,2:
128
+12@1Yf,2:
129
+~@1Zm,2:
130
+12@1_q,2:
131
+w@1ax,2:
132
+12@1bx,4:
133
+onH@2W,y:.
134
+
135
+
136
+Usage: </nowiki>[fossil clean]<nowiki> ?-all?
137
+
138
+DeletK@1jG,b@1fJ,2:
139
+y@1fz,2:
140
+q@1h0,5:
141
+
142
+v@1hw,2:
143
+y@1iv,1I:
144
+optional -all flag.
145
+
146
+
147
+Usage: </nowiki>[fossil clone]<nowiki> URL FILENAME
148
+
149
+v@1lt,1J:
150
+file named FILENAME.
151
+
152
+
153
+Usage: </nowiki>[fossil close]<nowiki> ?-f|--force?
154
+
155
+~@1op,2:
156
+10@1pt,1J:
157
+current check-out.
158
+
159
+
160
+Usage: </nowiki>[fossil configure]<nowiki> METHOD ...
161
+
162
+19@1t2,2:
163
+z@1uG,4:
164
+
165
+O@24~,S:export AREA FILENAME
166
+
167
+ 11@1v~,6:
168
+ l@1x1,4:
169
+
170
+O@24~,N:import FILENAME
171
+
172
+ ~@1yT,S:
173
+ configuration.
174
+
175
+O@24~,M:merge FILENAME
176
+
177
+ b@1yT,Q@200,6:
178
+ 12@20R,6:
179
+ U@21U,4:
180
+
181
+c@21~,8:
182
+
183
+ z@22d,6:
184
+ 10@23c,U:
185
+ server is used.
186
+
187
+c@24~,8:
188
+
189
+ 12@25d,6:
190
+ 11@26g,R:
191
+ this to work.
192
+
193
+O@24~,I:reset AREA
194
+
195
+ y@28a,4:
196
+
197
+17@29d,2:
198
+14@2Ap,2:
199
+Z@2By,19:
200
+
201
+
202
+COMMAND: deconstruct
203
+Usage: </nowiki>[fossil deconstruct]<nowiki>I@5UG,R:REPOSITORY? DESTINATION
204
+
205
+10@2FH,2:
206
+18@2GM,2:
207
+16@2HZ,2:
208
+O@2Ij,o:
209
+
210
+
211
+Usage: </nowiki>[fossil rm]<nowiki> FILE...
212
+P@2KT,2:
213
+c@2Kw,14:
214
+
215
+
216
+Usage: </nowiki>[fossil descendants]<nowiki> ?BASELINE-ID?
217
+
218
+16@2NU,2:
219
+n@2Oe,f:
220
+
221
+
222
+Usage: </nowiki>[fossil diff]<nowikiY@2Qi,4:
223
+
224
+10@2RL,2:
225
+u@2SQ,4:
226
+
227
+~@2TP,2:
228
+12@2UT,2:
229
+10@2V_,B:
230
+used.
231
+
232
+10@2Wp,2:
233
+K@2WG,E: executed.
234
+
235
+w@2YT,4:
236
+
237
+Y@2ZS,4:
238
+
239
+V@2_f,8:tkdiff
240
+c@2_f,2:
241
+V@2_f,F:tortoisemerge
242
+V@2_f,6:meld
243
+V@2_f,8:xxdiff
244
+V@2_f,r:kdiff3
245
+
246
+
247
+Usage: </nowiki>[fossil extra]<nowiki>
248
+
249
+11@2eI,2:
250
+L@1O~,V@2fi,s:
251
+
252
+
253
+Usage: </nowiki>[fossil help]<nowiki> COMMAND
254
+
255
+e@2hi,v:
256
+
257
+
258
+Usage: </nowiki>[fossil http]<nowiki> REPOSITORY
259
+
260
+17@2jv,2:
261
+16@2l6,2:
262
+12@2mH,1J:
263
+repository.
264
+
265
+
266
+Usage: </nowiki>[fossil info]<nowiki> ?ARTIFACT-ID|FILENAME?
267
+
268
+z@2pJ,2:
269
+11@2qM,2:
270
+~@2rS,2:
271
+u@2sW,2:
272
+I@4W,G@2tl,m:
273
+
274
+
275
+Usage: </nowiki>[fossil leaves]<nowiki>
276
+
277
+S@2vV,i:
278
+
279
+
280
+Usage: </nowiki>[fossil ls]<nowiki>
281
+
282
+o@2xE,t:
283
+
284
+
285
+Usage: </nowiki>[fossil merge]<nowiki> VERSION
286
+
287
+10@2za,G:
288
+checkout.
289
+
290
+y@2~v,2:
291
+11@30x,2:
292
+x@322,s:
293
+
294
+
295
+Usage: </nowiki>[fossil new]<nowiki> FILENAME
296
+
297
+11@3Af,2:
298
+11@3Bl,2:
299
+12@3Cr,t:
300
+
301
+
302
+Usage: </nowiki>[fossil open]<nowiki> FILENAME
303
+
304
+12@3FQ,2:
305
+15@3GX,2:
306
+T@3Hg,f:
307
+
308
+
309
+Usage: </nowiki>[fossil pull]<nowikia@3JQ,4:
310
+
311
+z@3K5,2:
312
+z@3L8,2:
313
+x@3MB,2:
314
+y@3NC,2:
315
+M@23~,a@3O_,2:
316
+f@3PE,4:
317
+
318
+X@3Pz,c:
319
+
320
+ http://USER@HOST:PORT/PATH
321
+
322
+l@3R5,2:
323
+w@3Rv,2:
324
+t@3Sv,2:
325
+v@3Ts,k:
326
+80.
327
+
328
+
329
+Usage: </nowiki>[fossil push]<nowiki_@3WB,4:
330
+
331
+13@3Wq,2:
332
+n@3Xy,w:
333
+
334
+Usage: </nowiki>[fossil rebuild]<nowiki> REPOSITORY
335
+
336
+s@3_R,2:
337
+p@3aN,2:
338
+q@3bG,6:
339
+
340
+
341
+9@40l,1G:reconstruct
342
+Usage: </nowiki>[fossil reconstruct]<nowiki> REPOSITORY ORIGIN
343
+
344
+11@3eV,2:
345
+R@3fa,y:
346
+
347
+
348
+Usage: </nowiki>[fossil redo]<nowiki> ?FILENAME...?
349
+
350
+11@3hc,2:
351
+10@3ii,2:
352
+10@3jn,M:
353
+or merge undone.
354
+
355
+z@3lD,2:
356
+k@3mG,h:
357
+
358
+
359
+Usage: </nowiki>[fossil revert]<nowikiS@3oN,4:
360
+
361
+s@3ou,2:
362
+x@3pq,2:
363
+y@3qr,2:
364
+h@3rt,i:
365
+
366
+
367
+Usage: </nowiki>[fossil server]<nowiki>X@3ul,2:
368
+m@3uW,4:
369
+
370
+14@3vN,2:
371
+x@3wW,2:
372
+14@3xX,2:
373
+12@3yf,G:
374
+within an open9@~D,5:.
375
+
376
+16@3~F,N:
377
+the web server.
378
+
379
+
380
+H@40l,u:
381
+COMMAND: unset
382
+Usage: </nowiki>[fossil setting]<nowikiU@42i,5:
383
+ Z@43C,4:
384
+
385
+16@43q,2:
386
+17@450,2:
387
+19@46C,4:
388
+
389
+j@47R,4:
390
+
391
+w@48C,I:
392
+ g@498,I:
393
+ g@49p,4:
394
+
395
+13@4AY,I:
396
+ r@4Bb,4:
397
+
398
+13@4CV,4:
399
+
400
+17@4Da,I:
401
+ k@4Ei,4:
402
+
403
+12@4FV,I:
404
+ k@4GY,I:
405
+ l@4HI,I:
406
+ f@4I3,4:
407
+
408
+16@4Il,I:
409
+ w@4Js,b:
410
+ be unsigned.
411
+
412
+15@4L6,I:
413
+ e@4MC,4:
414
+
415
+16@4Mt,I:
416
+ s@4N~,I:
417
+ s@4Os,I:
418
+ f@4Pk,4:
419
+
420
+11@4QS,I:
421
+ l@4RU,I:
422
+ n@4SF,1T:
423
+ and "firefox" on Unix.
424
+
425
+
426
+Usage: </nowiki>[fossil status]<nowiki>
427
+
428
+i@4Uw,f:
429
+
430
+
431
+Usage: </nowiki>[fossil sync]<nowiki_@3WB,4:
432
+
433
+13@4X_,2:
434
+12@4Yh,2:
435
+n@3Xy,y:
436
+
437
+
438
+Usage: </nowiki>[fossil tag]<nowiki> SUBCOMMAND ...
439
+
440
+O@5Ui,U@4bY,3:
441
+
442
+p@4c1,8:
443
+
444
+ s@4cs,6:
445
+ s@4dk,U:
446
+ update and merge.
447
+
448
+12@4ey,8:
449
+
450
+ n@4g1,6:
451
+ s@4gp,6:
452
+ n@4hh,6:
453
+ m@4iV,6:
454
+ o@4jH,6:
455
+ q@4k5,V:
456
+ be cancelled.
457
+
458
+ l@4lE,6:
459
+ q@4l~,6:
460
+ u@4mq,3:
461
+
462
+k@4nk,8:
463
+
464
+ u@4oW,6:
465
+ n@4pQ,3:
466
+
467
+_@4qD,8:
468
+
469
+ c@4qo,3:
470
+
471
+c@4rR,8:
472
+
473
+ o@4s4,2:
474
+8@4Cf,c@4sx,4:
475
+
476
+t@4te,2:
477
+r@4ub,2:
478
+u@4vX,2:
479
+O@4wV,4:
480
+
481
+t@4wy,2:
482
+u@4xv,2:
483
+v@4yt,T:
484
+
485
+ fossil update decaf
486
+
487
+w@4~H,2:
488
+v@50H,4:
489
+
490
+P@51F,4:
491
+
492
+j@51j,j:
493
+
494
+
495
+Usage: </nowiki>[fossil timeline]<nowikig@53v,4:
496
+
497
+x@54g,2:
498
+w@55h,2:
499
+v@56h,2:
500
+x@57g,a:
501
+keywords:
502
+
503
+ before
504
+ after
505
+R@59B,T:
506
+ ancestors | parents
507
+
508
+z@5A4,2:
509
+n@5B7,2:
510
+x@5Bz,2:
511
+G@5DW,b@5DF,y:
512
+
513
+
514
+Usage: </nowiki>[fossil undo]<nowiki> ?FILENAME...?
515
+
516
+~@5FS,2:
517
+15@5GW,2:
518
+_@5Hf,4:
519
+
520
+z@3lD,2:
521
+k@3mG,h:
522
+
523
+
524
+Usage: </nowiki>[fossil update]<nowikiM@5LU,4:
525
+
526
+11@5Lv,2:
527
+z@5N0,2:
528
+z@5O3,2:
529
+10@5P6,2:
530
+W@5QB,4:
531
+
532
+I@3Bl,i@5R3,2:
533
+t@5Rq,f:
534
+
535
+
536
+Usage: </nowiki>[fossil user]<nowikid@5T~,4:
537
+
538
+y@5Ui,2:
539
+w@5Vk,4:
540
+
541
+i@5Wi,7:
542
+
543
+ o@5XS,4:
544
+
545
+X@5YI,7:
546
+
547
+ L@5XS,b@5ZA,5:
548
+ b@5Zm,U:
549
+
550
+ fossil user list
551
+
552
+ f@5_k,4:
553
+
554
+T@5aS,7:
555
+
556
+ H@1XW,g@5bC,5:
557
+ 12@5bt,5:
558
+ T@5cw,4:
559
+
560
+W@5dR,7:
561
+
562
+ j@5dy,n:
563
+
564
+
565
+Usage: </nowiki>[fossil version]<nowiki>
566
+
567
+~@5gD,f:
568
+
569
+
570
+Usage: </nowiki>[fossil wiki]<nowikib@5iU,4:
571
+
572
+O@5Ui,P:to fetch wiki entries.
573
+
574
+H@5pl,M@5kA,7:
575
+
576
+ m@5kY,5:
577
+ k@5lK,3:
578
+
579
+H@5pl,5:commiH@5kF,7:
580
+
581
+ y@5mi,3:
582
+
583
+H@5pl,M@5nx,7:
584
+
585
+ H@1XW,e@5oa,5:
586
+ W@5pF,3:
587
+
588
+L@5pl,7:
589
+
590
+ m@5q7,5:
591
+ T@5qu,D:
592
+
593
+TODOs:
594
+
595
+H@5pl,_@5rp,7:
596
+
597
+ i@5sQ,3:
598
+
599
+H@5pl,S@5tP,7:
600
+
601
+ 11@5ts,5:
602
+ k@5uu,3:
603
+
604
+H@5pl,N@5vv,7:
605
+
606
+ ~@5wJ,5:
607
+ j@5xJ,3:
608
+
609
+H@5pl,i@5yJ,7:
610
+
611
+ 13@5z2,y:
612
+ to the head version).
613
+
614
+</pre></nowiki>
615
+
616
+<hr>
617
+
618
+G@600,2:
619
+10@60L,2:
620
+12@61Q,2:
621
+15@62X,2:
622
+v@63g,2:
623
+1E@64f,2:
624
+18@65y,2:
625
+17@67A,2:
626
+18@68M,2:
627
+14@69Z,2:
628
+16@6Ah,2:
629
+Q@6Bs,2MVVNy;
--- a/www/reference.wiki
+++ b/www/reference.wiki
@@ -0,0 +1,629 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/reference.wiki
+++ b/www/reference.wiki
@@ -0,0 +1,629 @@
1 of fossil as
2
3 The <code>fossil</code> program supplies most of the actual
4 documentation about its options, so a good way to start documenting
5 the program is to nab the output of <code>fossil help <i>command</i></code>
6 for all of its (exposed) cli.
7
8 <i>This was suggested under the <b>Reference</b> heading in
9 [Documentation outline].
10
11 SCM) systems—but not <i>too</i>
12 much.
13
14 If you are trying to (cl
15
16 rmation about fodoc/tip/www/ssil'
17 are trying to (cli)fossil as a shell you invnk orm">rmcl.
18 Think of fo
19 ">rmcl.
20 Think of fossil as i>distinct</i> prefix of A40 characte
21 ssil as a shell you invoke and feed a command to,
22 including any optionsnkeffectivel looking for that string | clone the repository formbthe repos
23 ry f </tr>
24
25 (Sut not <i>too</i>
26 much.
27
28 I
29 href="widel not <i>to2;aintenence (Smerge">mergeil Home</a> and
30 <a
31 ersion</u>]
32 in <b>fossil</b> is a 40-character loanges">changesa
33 enough(Smerge">mergeil Homals web
34 capabil
35
36 iki">Fossil Home</a> and
37 <a href="wie special delimiteat string | c
38 e>diff not <i>to2;aintenence
39
40 f not <i>to2
41 akethe-e�but not <i>too<n
42
43 Available COMMANDs:
44 add configuration leaves redo ui
45 all deconstruct ls rename undo
46 cgi del merge revert unset
47 changes descendants mv rm update
48 checkout diff new server user
49 ci extra openl as a s settings version
50 clean gdiff pull status wiki
51 clone help push sync
52 close http rebuild tag
53 commit info not <i </pre></nowiki>
54 nten
55 </pre></nowiki>
56 nc of A40 c haracter hexadecimal string.
57 ibu d environment c
58 ching.wiki | explanat that is d
59 fossil</b <tr>
60 ersion yommands do not use speconcepts.wiki#ke y
61 c | <u>versi <nowiki><pre>
62
63 -character longts.wiki#knk of fossil as a s
64 iki#knk of foss
65 <nowiki><pre>
66
67 Usage: </nowiki><code>[fossil add]</code><nowiki> FILE...
68
69 l makethe-e�but not <i>too<n
70 entered to make the intent unambigu
71 nk of fossil as a snvoke and feed a command to </nowiki><code>[fossil all]</code><nowikiV@11E,B:
72
73 The ~/.7@D~,C:file recordsX@15z,8: for a
74 13@12u,2:
75 17@141,2:
76 P@15D,4:
77
78 r@15e,4:
79
80 t@16Y,4:
81
82 j@17T,4:
83
84 e@18E,4:
85
86 j@18v,4:
87
88 16@19j,2:
89 17@1Au,1A:
90 pull, push, or sync
91
92
93 Usage: </nowiki>[fossil cgi]<nowiki> SCRIPT
94
95 10@1Dl,2:
96 z@1Eq,2:
97 11@1Ft,2:
98 13@1Gz,2:
99 h@1I6,T:
100
101 #!/usr/bin/fossil
102 e@1JA,4:
103
104 13@1Ju,2:
105 11@1L1,2:
106 m@1M7,n:
107
108
109 Usage: </nowiki>[fossil changes]<nowiki>
110
111 ~@1OL,2:
112 g@1PP,j:
113
114
115 Usage: </nowiki>[fossil checkout]<nowikiM@1RD,4:
116
117 10@1Re,2:
118 z@1Sj,2:
119 k@1Tm,4:
120
121 U@1Ub,h:
122
123
124 Usage: </nowiki>[fossil commit]<nowikiZ@1WS,5:
125 U@1X0,4:
126
127 11@1X_,2:
128 12@1Yf,2:
129 ~@1Zm,2:
130 12@1_q,2:
131 w@1ax,2:
132 12@1bx,4:
133 onH@2W,y:.
134
135
136 Usage: </nowiki>[fossil clean]<nowiki> ?-all?
137
138 DeletK@1jG,b@1fJ,2:
139 y@1fz,2:
140 q@1h0,5:
141
142 v@1hw,2:
143 y@1iv,1I:
144 optional -all flag.
145
146
147 Usage: </nowiki>[fossil clone]<nowiki> URL FILENAME
148
149 v@1lt,1J:
150 file named FILENAME.
151
152
153 Usage: </nowiki>[fossil close]<nowiki> ?-f|--force?
154
155 ~@1op,2:
156 10@1pt,1J:
157 current check-out.
158
159
160 Usage: </nowiki>[fossil configure]<nowiki> METHOD ...
161
162 19@1t2,2:
163 z@1uG,4:
164
165 O@24~,S:export AREA FILENAME
166
167 11@1v~,6:
168 l@1x1,4:
169
170 O@24~,N:import FILENAME
171
172 ~@1yT,S:
173 configuration.
174
175 O@24~,M:merge FILENAME
176
177 b@1yT,Q@200,6:
178 12@20R,6:
179 U@21U,4:
180
181 c@21~,8:
182
183 z@22d,6:
184 10@23c,U:
185 server is used.
186
187 c@24~,8:
188
189 12@25d,6:
190 11@26g,R:
191 this to work.
192
193 O@24~,I:reset AREA
194
195 y@28a,4:
196
197 17@29d,2:
198 14@2Ap,2:
199 Z@2By,19:
200
201
202 COMMAND: deconstruct
203 Usage: </nowiki>[fossil deconstruct]<nowiki>I@5UG,R:REPOSITORY? DESTINATION
204
205 10@2FH,2:
206 18@2GM,2:
207 16@2HZ,2:
208 O@2Ij,o:
209
210
211 Usage: </nowiki>[fossil rm]<nowiki> FILE...
212 P@2KT,2:
213 c@2Kw,14:
214
215
216 Usage: </nowiki>[fossil descendants]<nowiki> ?BASELINE-ID?
217
218 16@2NU,2:
219 n@2Oe,f:
220
221
222 Usage: </nowiki>[fossil diff]<nowikiY@2Qi,4:
223
224 10@2RL,2:
225 u@2SQ,4:
226
227 ~@2TP,2:
228 12@2UT,2:
229 10@2V_,B:
230 used.
231
232 10@2Wp,2:
233 K@2WG,E: executed.
234
235 w@2YT,4:
236
237 Y@2ZS,4:
238
239 V@2_f,8:tkdiff
240 c@2_f,2:
241 V@2_f,F:tortoisemerge
242 V@2_f,6:meld
243 V@2_f,8:xxdiff
244 V@2_f,r:kdiff3
245
246
247 Usage: </nowiki>[fossil extra]<nowiki>
248
249 11@2eI,2:
250 L@1O~,V@2fi,s:
251
252
253 Usage: </nowiki>[fossil help]<nowiki> COMMAND
254
255 e@2hi,v:
256
257
258 Usage: </nowiki>[fossil http]<nowiki> REPOSITORY
259
260 17@2jv,2:
261 16@2l6,2:
262 12@2mH,1J:
263 repository.
264
265
266 Usage: </nowiki>[fossil info]<nowiki> ?ARTIFACT-ID|FILENAME?
267
268 z@2pJ,2:
269 11@2qM,2:
270 ~@2rS,2:
271 u@2sW,2:
272 I@4W,G@2tl,m:
273
274
275 Usage: </nowiki>[fossil leaves]<nowiki>
276
277 S@2vV,i:
278
279
280 Usage: </nowiki>[fossil ls]<nowiki>
281
282 o@2xE,t:
283
284
285 Usage: </nowiki>[fossil merge]<nowiki> VERSION
286
287 10@2za,G:
288 checkout.
289
290 y@2~v,2:
291 11@30x,2:
292 x@322,s:
293
294
295 Usage: </nowiki>[fossil new]<nowiki> FILENAME
296
297 11@3Af,2:
298 11@3Bl,2:
299 12@3Cr,t:
300
301
302 Usage: </nowiki>[fossil open]<nowiki> FILENAME
303
304 12@3FQ,2:
305 15@3GX,2:
306 T@3Hg,f:
307
308
309 Usage: </nowiki>[fossil pull]<nowikia@3JQ,4:
310
311 z@3K5,2:
312 z@3L8,2:
313 x@3MB,2:
314 y@3NC,2:
315 M@23~,a@3O_,2:
316 f@3PE,4:
317
318 X@3Pz,c:
319
320 http://USER@HOST:PORT/PATH
321
322 l@3R5,2:
323 w@3Rv,2:
324 t@3Sv,2:
325 v@3Ts,k:
326 80.
327
328
329 Usage: </nowiki>[fossil push]<nowiki_@3WB,4:
330
331 13@3Wq,2:
332 n@3Xy,w:
333
334 Usage: </nowiki>[fossil rebuild]<nowiki> REPOSITORY
335
336 s@3_R,2:
337 p@3aN,2:
338 q@3bG,6:
339
340
341 9@40l,1G:reconstruct
342 Usage: </nowiki>[fossil reconstruct]<nowiki> REPOSITORY ORIGIN
343
344 11@3eV,2:
345 R@3fa,y:
346
347
348 Usage: </nowiki>[fossil redo]<nowiki> ?FILENAME...?
349
350 11@3hc,2:
351 10@3ii,2:
352 10@3jn,M:
353 or merge undone.
354
355 z@3lD,2:
356 k@3mG,h:
357
358
359 Usage: </nowiki>[fossil revert]<nowikiS@3oN,4:
360
361 s@3ou,2:
362 x@3pq,2:
363 y@3qr,2:
364 h@3rt,i:
365
366
367 Usage: </nowiki>[fossil server]<nowiki>X@3ul,2:
368 m@3uW,4:
369
370 14@3vN,2:
371 x@3wW,2:
372 14@3xX,2:
373 12@3yf,G:
374 within an open9@~D,5:.
375
376 16@3~F,N:
377 the web server.
378
379
380 H@40l,u:
381 COMMAND: unset
382 Usage: </nowiki>[fossil setting]<nowikiU@42i,5:
383 Z@43C,4:
384
385 16@43q,2:
386 17@450,2:
387 19@46C,4:
388
389 j@47R,4:
390
391 w@48C,I:
392 g@498,I:
393 g@49p,4:
394
395 13@4AY,I:
396 r@4Bb,4:
397
398 13@4CV,4:
399
400 17@4Da,I:
401 k@4Ei,4:
402
403 12@4FV,I:
404 k@4GY,I:
405 l@4HI,I:
406 f@4I3,4:
407
408 16@4Il,I:
409 w@4Js,b:
410 be unsigned.
411
412 15@4L6,I:
413 e@4MC,4:
414
415 16@4Mt,I:
416 s@4N~,I:
417 s@4Os,I:
418 f@4Pk,4:
419
420 11@4QS,I:
421 l@4RU,I:
422 n@4SF,1T:
423 and "firefox" on Unix.
424
425
426 Usage: </nowiki>[fossil status]<nowiki>
427
428 i@4Uw,f:
429
430
431 Usage: </nowiki>[fossil sync]<nowiki_@3WB,4:
432
433 13@4X_,2:
434 12@4Yh,2:
435 n@3Xy,y:
436
437
438 Usage: </nowiki>[fossil tag]<nowiki> SUBCOMMAND ...
439
440 O@5Ui,U@4bY,3:
441
442 p@4c1,8:
443
444 s@4cs,6:
445 s@4dk,U:
446 update and merge.
447
448 12@4ey,8:
449
450 n@4g1,6:
451 s@4gp,6:
452 n@4hh,6:
453 m@4iV,6:
454 o@4jH,6:
455 q@4k5,V:
456 be cancelled.
457
458 l@4lE,6:
459 q@4l~,6:
460 u@4mq,3:
461
462 k@4nk,8:
463
464 u@4oW,6:
465 n@4pQ,3:
466
467 _@4qD,8:
468
469 c@4qo,3:
470
471 c@4rR,8:
472
473 o@4s4,2:
474 8@4Cf,c@4sx,4:
475
476 t@4te,2:
477 r@4ub,2:
478 u@4vX,2:
479 O@4wV,4:
480
481 t@4wy,2:
482 u@4xv,2:
483 v@4yt,T:
484
485 fossil update decaf
486
487 w@4~H,2:
488 v@50H,4:
489
490 P@51F,4:
491
492 j@51j,j:
493
494
495 Usage: </nowiki>[fossil timeline]<nowikig@53v,4:
496
497 x@54g,2:
498 w@55h,2:
499 v@56h,2:
500 x@57g,a:
501 keywords:
502
503 before
504 after
505 R@59B,T:
506 ancestors | parents
507
508 z@5A4,2:
509 n@5B7,2:
510 x@5Bz,2:
511 G@5DW,b@5DF,y:
512
513
514 Usage: </nowiki>[fossil undo]<nowiki> ?FILENAME...?
515
516 ~@5FS,2:
517 15@5GW,2:
518 _@5Hf,4:
519
520 z@3lD,2:
521 k@3mG,h:
522
523
524 Usage: </nowiki>[fossil update]<nowikiM@5LU,4:
525
526 11@5Lv,2:
527 z@5N0,2:
528 z@5O3,2:
529 10@5P6,2:
530 W@5QB,4:
531
532 I@3Bl,i@5R3,2:
533 t@5Rq,f:
534
535
536 Usage: </nowiki>[fossil user]<nowikid@5T~,4:
537
538 y@5Ui,2:
539 w@5Vk,4:
540
541 i@5Wi,7:
542
543 o@5XS,4:
544
545 X@5YI,7:
546
547 L@5XS,b@5ZA,5:
548 b@5Zm,U:
549
550 fossil user list
551
552 f@5_k,4:
553
554 T@5aS,7:
555
556 H@1XW,g@5bC,5:
557 12@5bt,5:
558 T@5cw,4:
559
560 W@5dR,7:
561
562 j@5dy,n:
563
564
565 Usage: </nowiki>[fossil version]<nowiki>
566
567 ~@5gD,f:
568
569
570 Usage: </nowiki>[fossil wiki]<nowikib@5iU,4:
571
572 O@5Ui,P:to fetch wiki entries.
573
574 H@5pl,M@5kA,7:
575
576 m@5kY,5:
577 k@5lK,3:
578
579 H@5pl,5:commiH@5kF,7:
580
581 y@5mi,3:
582
583 H@5pl,M@5nx,7:
584
585 H@1XW,e@5oa,5:
586 W@5pF,3:
587
588 L@5pl,7:
589
590 m@5q7,5:
591 T@5qu,D:
592
593 TODOs:
594
595 H@5pl,_@5rp,7:
596
597 i@5sQ,3:
598
599 H@5pl,S@5tP,7:
600
601 11@5ts,5:
602 k@5uu,3:
603
604 H@5pl,N@5vv,7:
605
606 ~@5wJ,5:
607 j@5xJ,3:
608
609 H@5pl,i@5yJ,7:
610
611 13@5z2,y:
612 to the head version).
613
614 </pre></nowiki>
615
616 <hr>
617
618 G@600,2:
619 10@60L,2:
620 12@61Q,2:
621 15@62X,2:
622 v@63g,2:
623 1E@64f,2:
624 18@65y,2:
625 17@67A,2:
626 18@68M,2:
627 14@69Z,2:
628 16@6Ah,2:
629 Q@6Bs,2MVVNy;

Keyboard Shortcuts

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