Fossil SCM
Fix documentation typos.
Commit
b78ca10222c8b0499e13195f31a6b5f53185627b
Parent
7a44fddd3f85902…
4 files changed
+1
-1
+1
-1
+1
-1
+1
-1
+1
-1
| --- www/concepts.wiki | ||
| +++ www/concepts.wiki | ||
| @@ -405,11 +405,11 @@ | ||
| 405 | 405 | can do pushes or pulls against your server. Use the <b>--port</b> |
| 406 | 406 | option to the server command to specify a different TCP port. If |
| 407 | 407 | you do not have a local source tree, use the <b>-R</b> command-line |
| 408 | 408 | option to specify the repository file. |
| 409 | 409 | |
| 410 | -A stand-alone server is a great way to set of transient connections | |
| 410 | +The "fossil server" command is a great way to set of transient connections | |
| 411 | 411 | between coworkers for doing quick pushes or pulls. But you can also |
| 412 | 412 | set up a permanent stand-alone server if you prefer. Just make |
| 413 | 413 | arrangements for fossil to be launched with appropriate arguments |
| 414 | 414 | after every reboot. |
| 415 | 415 | |
| 416 | 416 |
| --- www/concepts.wiki | |
| +++ www/concepts.wiki | |
| @@ -405,11 +405,11 @@ | |
| 405 | can do pushes or pulls against your server. Use the <b>--port</b> |
| 406 | option to the server command to specify a different TCP port. If |
| 407 | you do not have a local source tree, use the <b>-R</b> command-line |
| 408 | option to specify the repository file. |
| 409 | |
| 410 | A stand-alone server is a great way to set of transient connections |
| 411 | between coworkers for doing quick pushes or pulls. But you can also |
| 412 | set up a permanent stand-alone server if you prefer. Just make |
| 413 | arrangements for fossil to be launched with appropriate arguments |
| 414 | after every reboot. |
| 415 | |
| 416 |
| --- www/concepts.wiki | |
| +++ www/concepts.wiki | |
| @@ -405,11 +405,11 @@ | |
| 405 | can do pushes or pulls against your server. Use the <b>--port</b> |
| 406 | option to the server command to specify a different TCP port. If |
| 407 | you do not have a local source tree, use the <b>-R</b> command-line |
| 408 | option to specify the repository file. |
| 409 | |
| 410 | The "fossil server" command is a great way to set of transient connections |
| 411 | between coworkers for doing quick pushes or pulls. But you can also |
| 412 | set up a permanent stand-alone server if you prefer. Just make |
| 413 | arrangements for fossil to be launched with appropriate arguments |
| 414 | after every reboot. |
| 415 | |
| 416 |
+1
-1
| --- www/foss-cklist.wiki | ||
| +++ www/foss-cklist.wiki | ||
| @@ -5,11 +5,11 @@ | ||
| 5 | 5 | blog post <a href="http://spot.livejournal.com/308370.html"> |
| 6 | 6 | http://spot.livejournal.com/308370.html</a> (see also |
| 7 | 7 | <a href="http://www.theopensourceway.org/book/The_Open_Source_Way-How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL.html">[1]</a> and |
| 8 | 8 | <a href="https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL">[2]</a>). |
| 9 | 9 | Tom's original post assigned point scores to the various elements and |
| 10 | -by adding together the individual points, the reader is suppose to be able | |
| 10 | +by adding together the individual points, the reader is supposed to be able | |
| 11 | 11 | to judge the likelihood that the project will fail. |
| 12 | 12 | The point scores, and the items on the list, clearly reflect Tom's |
| 13 | 13 | biases and are not necessarily those of the larger open-source community. |
| 14 | 14 | Nevertheless, the policy of the Fossil shall be to strive for a perfect |
| 15 | 15 | score.</p> |
| 16 | 16 |
| --- www/foss-cklist.wiki | |
| +++ www/foss-cklist.wiki | |
| @@ -5,11 +5,11 @@ | |
| 5 | blog post <a href="http://spot.livejournal.com/308370.html"> |
| 6 | http://spot.livejournal.com/308370.html</a> (see also |
| 7 | <a href="http://www.theopensourceway.org/book/The_Open_Source_Way-How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL.html">[1]</a> and |
| 8 | <a href="https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL">[2]</a>). |
| 9 | Tom's original post assigned point scores to the various elements and |
| 10 | by adding together the individual points, the reader is suppose to be able |
| 11 | to judge the likelihood that the project will fail. |
| 12 | The point scores, and the items on the list, clearly reflect Tom's |
| 13 | biases and are not necessarily those of the larger open-source community. |
| 14 | Nevertheless, the policy of the Fossil shall be to strive for a perfect |
| 15 | score.</p> |
| 16 |
| --- www/foss-cklist.wiki | |
| +++ www/foss-cklist.wiki | |
| @@ -5,11 +5,11 @@ | |
| 5 | blog post <a href="http://spot.livejournal.com/308370.html"> |
| 6 | http://spot.livejournal.com/308370.html</a> (see also |
| 7 | <a href="http://www.theopensourceway.org/book/The_Open_Source_Way-How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL.html">[1]</a> and |
| 8 | <a href="https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL">[2]</a>). |
| 9 | Tom's original post assigned point scores to the various elements and |
| 10 | by adding together the individual points, the reader is supposed to be able |
| 11 | to judge the likelihood that the project will fail. |
| 12 | The point scores, and the items on the list, clearly reflect Tom's |
| 13 | biases and are not necessarily those of the larger open-source community. |
| 14 | Nevertheless, the policy of the Fossil shall be to strive for a perfect |
| 15 | score.</p> |
| 16 |
+1
-1
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -185,11 +185,11 @@ | ||
| 185 | 185 | between repositories and working checkouts. A power-loss or system crash |
| 186 | 186 | in the middle of Git operation can damage or corrupt the Git repository. |
| 187 | 187 | |
| 188 | 188 | A Fossil repository consists of a single disk file. A single Fossil |
| 189 | 189 | repository can serve multiple simultaneous working checkouts. |
| 190 | -A Fossil repository is an SQLite database, so it highly resistant | |
| 190 | +A Fossil repository is an SQLite database, so it is highly resistant | |
| 191 | 191 | to damage from a power-loss or system crash - incomplete transactions |
| 192 | 192 | are simply rolled back after the system reboots. |
| 193 | 193 | |
| 194 | 194 | <h3>3.8 Audit Trail</h3> |
| 195 | 195 | |
| 196 | 196 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -185,11 +185,11 @@ | |
| 185 | between repositories and working checkouts. A power-loss or system crash |
| 186 | in the middle of Git operation can damage or corrupt the Git repository. |
| 187 | |
| 188 | A Fossil repository consists of a single disk file. A single Fossil |
| 189 | repository can serve multiple simultaneous working checkouts. |
| 190 | A Fossil repository is an SQLite database, so it highly resistant |
| 191 | to damage from a power-loss or system crash - incomplete transactions |
| 192 | are simply rolled back after the system reboots. |
| 193 | |
| 194 | <h3>3.8 Audit Trail</h3> |
| 195 | |
| 196 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -185,11 +185,11 @@ | |
| 185 | between repositories and working checkouts. A power-loss or system crash |
| 186 | in the middle of Git operation can damage or corrupt the Git repository. |
| 187 | |
| 188 | A Fossil repository consists of a single disk file. A single Fossil |
| 189 | repository can serve multiple simultaneous working checkouts. |
| 190 | A Fossil repository is an SQLite database, so it is highly resistant |
| 191 | to damage from a power-loss or system crash - incomplete transactions |
| 192 | are simply rolled back after the system reboots. |
| 193 | |
| 194 | <h3>3.8 Audit Trail</h3> |
| 195 | |
| 196 |
+1
-1
| --- www/server.wiki | ||
| +++ www/server.wiki | ||
| @@ -70,11 +70,11 @@ | ||
| 70 | 70 | need to modify the pathnames for your particular setup. |
| 71 | 71 | The final argument is either the name of the fossil repository to be served, |
| 72 | 72 | or a directory containing multiple repositories. |
| 73 | 73 | </p> |
| 74 | 74 | <p> |
| 75 | -If you system is running xinetd, then the configuration is likely to be | |
| 75 | +If your system is running xinetd, then the configuration is likely to be | |
| 76 | 76 | in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d". |
| 77 | 77 | An xinetd configuration file will appear like this:</p> |
| 78 | 78 | <blockquote> |
| 79 | 79 | <pre> |
| 80 | 80 | service http-alt |
| 81 | 81 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -70,11 +70,11 @@ | |
| 70 | need to modify the pathnames for your particular setup. |
| 71 | The final argument is either the name of the fossil repository to be served, |
| 72 | or a directory containing multiple repositories. |
| 73 | </p> |
| 74 | <p> |
| 75 | If you system is running xinetd, then the configuration is likely to be |
| 76 | in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d". |
| 77 | An xinetd configuration file will appear like this:</p> |
| 78 | <blockquote> |
| 79 | <pre> |
| 80 | service http-alt |
| 81 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -70,11 +70,11 @@ | |
| 70 | need to modify the pathnames for your particular setup. |
| 71 | The final argument is either the name of the fossil repository to be served, |
| 72 | or a directory containing multiple repositories. |
| 73 | </p> |
| 74 | <p> |
| 75 | If your system is running xinetd, then the configuration is likely to be |
| 76 | in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d". |
| 77 | An xinetd configuration file will appear like this:</p> |
| 78 | <blockquote> |
| 79 | <pre> |
| 80 | service http-alt |
| 81 |