Fossil SCM
fixed more typos and grammatical errors in WWW-docs as specified by ML-posted patches
Commit
bf1b99723e32418ad5bd0fe5fcd07c789d13f73e
Parent
05fc09c5ddc1b00…
14 files changed
+3
-3
+4
-4
+1
-1
+1
-1
+5
-5
+3
-3
+1
-1
+2
-2
+2
-2
+1
-1
+1
-1
+1
-1
+3
-3
+1
-1
+3
-3
| --- www/build.wiki | ||
| +++ www/build.wiki | ||
| @@ -78,11 +78,11 @@ | ||
| 78 | 78 | <ol> |
| 79 | 79 | <li value="5"> |
| 80 | 80 | <p>Unpack the ZIP or tarball you downloaded then |
| 81 | 81 | <b>cd</b> into the directory created.</p></li> |
| 82 | 82 | |
| 83 | -<li><i>(Optional, unix only)</i> | |
| 83 | +<li><i>(Optional, Unix only)</i> | |
| 84 | 84 | Run <b>./configure</b> to construct a makefile. |
| 85 | 85 | |
| 86 | 86 | <ol type="a"> |
| 87 | 87 | <li><p> |
| 88 | 88 | If you do not have the OpenSSL library installed on your system, then |
| @@ -100,11 +100,11 @@ | ||
| 100 | 100 | <li><p>Run "<b>make</b>" to build the "fossil" or "fossil.exe" executable. |
| 101 | 101 | The details depend on your platform and compiler. |
| 102 | 102 | |
| 103 | 103 | <ol type="a"> |
| 104 | 104 | <li><p><i>Unix</i> → the configure-generated Makefile should work on |
| 105 | -all unix and unix-like systems. Simply type "<b>make</b>". | |
| 105 | +all Unix and Unix-like systems. Simply type "<b>make</b>". | |
| 106 | 106 | |
| 107 | 107 | <li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you |
| 108 | 108 | can also use: <b>make -f Makefile.classic</b>. You may want to make minor |
| 109 | 109 | edits to Makefile.classic to configure the build for your system. |
| 110 | 110 | |
| @@ -132,11 +132,11 @@ | ||
| 132 | 132 | </pre></blockquote> |
| 133 | 133 | <blockquote><pre> |
| 134 | 134 | buildmsvc.bat FOSSIL_ENABLE_SSL=1 FOSSIL_BUILD_SSL=1 PERLDIR=C:\full\path\to\Perl\bin |
| 135 | 135 | </pre></blockquote> |
| 136 | 136 | |
| 137 | -<li><p><i>Cygwin</i> → The same as other unix-like systems. It is | |
| 137 | +<li><p><i>Cygwin</i> → The same as other Unix-like systems. It is | |
| 138 | 138 | recommended to configure using: "<b>configure --disable-internal-sqlite</b>", |
| 139 | 139 | making sure you have the "libsqlite3-devel" , "zlib-devel" and |
| 140 | 140 | "openssl-devel" packages installed first. |
| 141 | 141 | </ol> |
| 142 | 142 | </ol> |
| 143 | 143 |
| --- www/build.wiki | |
| +++ www/build.wiki | |
| @@ -78,11 +78,11 @@ | |
| 78 | <ol> |
| 79 | <li value="5"> |
| 80 | <p>Unpack the ZIP or tarball you downloaded then |
| 81 | <b>cd</b> into the directory created.</p></li> |
| 82 | |
| 83 | <li><i>(Optional, unix only)</i> |
| 84 | Run <b>./configure</b> to construct a makefile. |
| 85 | |
| 86 | <ol type="a"> |
| 87 | <li><p> |
| 88 | If you do not have the OpenSSL library installed on your system, then |
| @@ -100,11 +100,11 @@ | |
| 100 | <li><p>Run "<b>make</b>" to build the "fossil" or "fossil.exe" executable. |
| 101 | The details depend on your platform and compiler. |
| 102 | |
| 103 | <ol type="a"> |
| 104 | <li><p><i>Unix</i> → the configure-generated Makefile should work on |
| 105 | all unix and unix-like systems. Simply type "<b>make</b>". |
| 106 | |
| 107 | <li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you |
| 108 | can also use: <b>make -f Makefile.classic</b>. You may want to make minor |
| 109 | edits to Makefile.classic to configure the build for your system. |
| 110 | |
| @@ -132,11 +132,11 @@ | |
| 132 | </pre></blockquote> |
| 133 | <blockquote><pre> |
| 134 | buildmsvc.bat FOSSIL_ENABLE_SSL=1 FOSSIL_BUILD_SSL=1 PERLDIR=C:\full\path\to\Perl\bin |
| 135 | </pre></blockquote> |
| 136 | |
| 137 | <li><p><i>Cygwin</i> → The same as other unix-like systems. It is |
| 138 | recommended to configure using: "<b>configure --disable-internal-sqlite</b>", |
| 139 | making sure you have the "libsqlite3-devel" , "zlib-devel" and |
| 140 | "openssl-devel" packages installed first. |
| 141 | </ol> |
| 142 | </ol> |
| 143 |
| --- www/build.wiki | |
| +++ www/build.wiki | |
| @@ -78,11 +78,11 @@ | |
| 78 | <ol> |
| 79 | <li value="5"> |
| 80 | <p>Unpack the ZIP or tarball you downloaded then |
| 81 | <b>cd</b> into the directory created.</p></li> |
| 82 | |
| 83 | <li><i>(Optional, Unix only)</i> |
| 84 | Run <b>./configure</b> to construct a makefile. |
| 85 | |
| 86 | <ol type="a"> |
| 87 | <li><p> |
| 88 | If you do not have the OpenSSL library installed on your system, then |
| @@ -100,11 +100,11 @@ | |
| 100 | <li><p>Run "<b>make</b>" to build the "fossil" or "fossil.exe" executable. |
| 101 | The details depend on your platform and compiler. |
| 102 | |
| 103 | <ol type="a"> |
| 104 | <li><p><i>Unix</i> → the configure-generated Makefile should work on |
| 105 | all Unix and Unix-like systems. Simply type "<b>make</b>". |
| 106 | |
| 107 | <li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you |
| 108 | can also use: <b>make -f Makefile.classic</b>. You may want to make minor |
| 109 | edits to Makefile.classic to configure the build for your system. |
| 110 | |
| @@ -132,11 +132,11 @@ | |
| 132 | </pre></blockquote> |
| 133 | <blockquote><pre> |
| 134 | buildmsvc.bat FOSSIL_ENABLE_SSL=1 FOSSIL_BUILD_SSL=1 PERLDIR=C:\full\path\to\Perl\bin |
| 135 | </pre></blockquote> |
| 136 | |
| 137 | <li><p><i>Cygwin</i> → The same as other Unix-like systems. It is |
| 138 | recommended to configure using: "<b>configure --disable-internal-sqlite</b>", |
| 139 | making sure you have the "libsqlite3-devel" , "zlib-devel" and |
| 140 | "openssl-devel" packages installed first. |
| 141 | </ol> |
| 142 | </ol> |
| 143 |
+4
-4
| --- www/changes.wiki | ||
| +++ www/changes.wiki | ||
| @@ -246,11 +246,11 @@ | ||
| 246 | 246 | * Renamed <tt>/stats_report</tt> page to [/reports]. Graph width is now |
| 247 | 247 | relative, not absolute. |
| 248 | 248 | * Added <tt>yw=YYYY-WW</tt> (year-week) filter to timeline to limit the results |
| 249 | 249 | to a specific year and calendar week number, e.g. [/timeline?yw=2013-01]. |
| 250 | 250 | * Updates to SQLite to prevent opening a repository file using file descriptors |
| 251 | - 1 or 2 on unix. This fixes a bug under which an assertion failure could | |
| 251 | + 1 or 2 on Unix. This fixes a bug under which an assertion failure could | |
| 252 | 252 | overwrite part of a repository database file, corrupting it. |
| 253 | 253 | * Added support for unlimited line lengths in side-by-side diffs. |
| 254 | 254 | * New --close option to [/help?cmd=commit | fossil commit], which |
| 255 | 255 | immediately closes the branch being committed. |
| 256 | 256 | * Added <tt>chart</tt> option to [/help?cmd=bisect | fossil bisect]. |
| @@ -269,11 +269,11 @@ | ||
| 269 | 269 | [/help?cmd=server | fossil server] commands can take an IP address in addition |
| 270 | 270 | to the port number, causing Fossil to bind to just that one IP address. |
| 271 | 271 | * After prompting for a password, also ask if that password should be |
| 272 | 272 | remembered. |
| 273 | 273 | * Performance improvements to the diff engine. |
| 274 | - * Fix the side-by-side diff engine to work better with multi-byte unicode text. | |
| 274 | + * Fix the side-by-side diff engine to work better with multi-byte Unicode text. | |
| 275 | 275 | * Color-coding in the web-based annotation (blame) display. Fix the annotation |
| 276 | 276 | engine so that it is no longer confused by time-warps. |
| 277 | 277 | * The markdown formatter is now available by default and can be used for |
| 278 | 278 | tickets, wiki, and embedded documentation. |
| 279 | 279 | * Add subcommands "fossil bisect log" and "fossil bisect status" to the |
| @@ -466,11 +466,11 @@ | ||
| 466 | 466 | * Merge the latest SQLite changes from upstream. |
| 467 | 467 | * Lots of minor bug fixes. |
| 468 | 468 | |
| 469 | 469 | <h2>Changes For Version 1.23 (2012-08-08)</h2> |
| 470 | 470 | * The default checkout database name is now ".fslckout" instead of |
| 471 | - "_FOSSIL_" on unix. Both names continue to work. | |
| 471 | + "_FOSSIL_" on Unix. Both names continue to work. | |
| 472 | 472 | * Added the "fossil all changes" command |
| 473 | 473 | * Added the --ckout option to the "fossil all list" command |
| 474 | 474 | * Added the "public-pages" glob pattern that can be configured to allow |
| 475 | 475 | anonymous users to see embedded documentation on sites where source |
| 476 | 476 | code should not be accessible to anonymous users. |
| @@ -606,11 +606,11 @@ | ||
| 606 | 606 | * Added support for client-side SSL certificates with "ssl-identity" |
| 607 | 607 | setting and --ssl-identity option. |
| 608 | 608 | * Added "ssl-ca-location" setting to specify trusted root |
| 609 | 609 | SSL certificates. |
| 610 | 610 | * Added the --case-sensitive BOOLEAN command-line option to many commands. |
| 611 | - Default to true for unix and false for windows. | |
| 611 | + Default to true for Unix and false for windows. | |
| 612 | 612 | * Added the "Color-Test" submenu button on the branch list web page. |
| 613 | 613 | * Compatibility improvements to the git-export feature. |
| 614 | 614 | * Performance improvements on SHA1 checksums |
| 615 | 615 | * Update to the latest SQLite version 3.7.8 alpha. |
| 616 | 616 | * Fix the tarball generator to work with very log pathnames |
| 617 | 617 |
| --- www/changes.wiki | |
| +++ www/changes.wiki | |
| @@ -246,11 +246,11 @@ | |
| 246 | * Renamed <tt>/stats_report</tt> page to [/reports]. Graph width is now |
| 247 | relative, not absolute. |
| 248 | * Added <tt>yw=YYYY-WW</tt> (year-week) filter to timeline to limit the results |
| 249 | to a specific year and calendar week number, e.g. [/timeline?yw=2013-01]. |
| 250 | * Updates to SQLite to prevent opening a repository file using file descriptors |
| 251 | 1 or 2 on unix. This fixes a bug under which an assertion failure could |
| 252 | overwrite part of a repository database file, corrupting it. |
| 253 | * Added support for unlimited line lengths in side-by-side diffs. |
| 254 | * New --close option to [/help?cmd=commit | fossil commit], which |
| 255 | immediately closes the branch being committed. |
| 256 | * Added <tt>chart</tt> option to [/help?cmd=bisect | fossil bisect]. |
| @@ -269,11 +269,11 @@ | |
| 269 | [/help?cmd=server | fossil server] commands can take an IP address in addition |
| 270 | to the port number, causing Fossil to bind to just that one IP address. |
| 271 | * After prompting for a password, also ask if that password should be |
| 272 | remembered. |
| 273 | * Performance improvements to the diff engine. |
| 274 | * Fix the side-by-side diff engine to work better with multi-byte unicode text. |
| 275 | * Color-coding in the web-based annotation (blame) display. Fix the annotation |
| 276 | engine so that it is no longer confused by time-warps. |
| 277 | * The markdown formatter is now available by default and can be used for |
| 278 | tickets, wiki, and embedded documentation. |
| 279 | * Add subcommands "fossil bisect log" and "fossil bisect status" to the |
| @@ -466,11 +466,11 @@ | |
| 466 | * Merge the latest SQLite changes from upstream. |
| 467 | * Lots of minor bug fixes. |
| 468 | |
| 469 | <h2>Changes For Version 1.23 (2012-08-08)</h2> |
| 470 | * The default checkout database name is now ".fslckout" instead of |
| 471 | "_FOSSIL_" on unix. Both names continue to work. |
| 472 | * Added the "fossil all changes" command |
| 473 | * Added the --ckout option to the "fossil all list" command |
| 474 | * Added the "public-pages" glob pattern that can be configured to allow |
| 475 | anonymous users to see embedded documentation on sites where source |
| 476 | code should not be accessible to anonymous users. |
| @@ -606,11 +606,11 @@ | |
| 606 | * Added support for client-side SSL certificates with "ssl-identity" |
| 607 | setting and --ssl-identity option. |
| 608 | * Added "ssl-ca-location" setting to specify trusted root |
| 609 | SSL certificates. |
| 610 | * Added the --case-sensitive BOOLEAN command-line option to many commands. |
| 611 | Default to true for unix and false for windows. |
| 612 | * Added the "Color-Test" submenu button on the branch list web page. |
| 613 | * Compatibility improvements to the git-export feature. |
| 614 | * Performance improvements on SHA1 checksums |
| 615 | * Update to the latest SQLite version 3.7.8 alpha. |
| 616 | * Fix the tarball generator to work with very log pathnames |
| 617 |
| --- www/changes.wiki | |
| +++ www/changes.wiki | |
| @@ -246,11 +246,11 @@ | |
| 246 | * Renamed <tt>/stats_report</tt> page to [/reports]. Graph width is now |
| 247 | relative, not absolute. |
| 248 | * Added <tt>yw=YYYY-WW</tt> (year-week) filter to timeline to limit the results |
| 249 | to a specific year and calendar week number, e.g. [/timeline?yw=2013-01]. |
| 250 | * Updates to SQLite to prevent opening a repository file using file descriptors |
| 251 | 1 or 2 on Unix. This fixes a bug under which an assertion failure could |
| 252 | overwrite part of a repository database file, corrupting it. |
| 253 | * Added support for unlimited line lengths in side-by-side diffs. |
| 254 | * New --close option to [/help?cmd=commit | fossil commit], which |
| 255 | immediately closes the branch being committed. |
| 256 | * Added <tt>chart</tt> option to [/help?cmd=bisect | fossil bisect]. |
| @@ -269,11 +269,11 @@ | |
| 269 | [/help?cmd=server | fossil server] commands can take an IP address in addition |
| 270 | to the port number, causing Fossil to bind to just that one IP address. |
| 271 | * After prompting for a password, also ask if that password should be |
| 272 | remembered. |
| 273 | * Performance improvements to the diff engine. |
| 274 | * Fix the side-by-side diff engine to work better with multi-byte Unicode text. |
| 275 | * Color-coding in the web-based annotation (blame) display. Fix the annotation |
| 276 | engine so that it is no longer confused by time-warps. |
| 277 | * The markdown formatter is now available by default and can be used for |
| 278 | tickets, wiki, and embedded documentation. |
| 279 | * Add subcommands "fossil bisect log" and "fossil bisect status" to the |
| @@ -466,11 +466,11 @@ | |
| 466 | * Merge the latest SQLite changes from upstream. |
| 467 | * Lots of minor bug fixes. |
| 468 | |
| 469 | <h2>Changes For Version 1.23 (2012-08-08)</h2> |
| 470 | * The default checkout database name is now ".fslckout" instead of |
| 471 | "_FOSSIL_" on Unix. Both names continue to work. |
| 472 | * Added the "fossil all changes" command |
| 473 | * Added the --ckout option to the "fossil all list" command |
| 474 | * Added the "public-pages" glob pattern that can be configured to allow |
| 475 | anonymous users to see embedded documentation on sites where source |
| 476 | code should not be accessible to anonymous users. |
| @@ -606,11 +606,11 @@ | |
| 606 | * Added support for client-side SSL certificates with "ssl-identity" |
| 607 | setting and --ssl-identity option. |
| 608 | * Added "ssl-ca-location" setting to specify trusted root |
| 609 | SSL certificates. |
| 610 | * Added the --case-sensitive BOOLEAN command-line option to many commands. |
| 611 | Default to true for Unix and false for windows. |
| 612 | * Added the "Color-Test" submenu button on the branch list web page. |
| 613 | * Compatibility improvements to the git-export feature. |
| 614 | * Performance improvements on SHA1 checksums |
| 615 | * Update to the latest SQLite version 3.7.8 alpha. |
| 616 | * Fix the tarball generator to work with very log pathnames |
| 617 |
+1
-1
| --- www/contribute.wiki | ||
| +++ www/contribute.wiki | ||
| @@ -15,11 +15,11 @@ | ||
| 15 | 15 | and other lawyer-rich organizations require this as a precondition to using |
| 16 | 16 | Fossil. |
| 17 | 17 | |
| 18 | 18 | If you do not wish to submit a Contributor Agreement, we would still |
| 19 | 19 | welcome your suggestions and example code, but we will not use your code |
| 20 | -directly - we will be forced to reimplement your changes from scratch which | |
| 20 | +directly - we will be forced to re-implement your changes from scratch which | |
| 21 | 21 | might take longer. |
| 22 | 22 | |
| 23 | 23 | <h2>2.0 Submitting Patches</h2> |
| 24 | 24 | |
| 25 | 25 | Suggested changes or bug fixes can be submitted by creating a patch |
| 26 | 26 |
| --- www/contribute.wiki | |
| +++ www/contribute.wiki | |
| @@ -15,11 +15,11 @@ | |
| 15 | and other lawyer-rich organizations require this as a precondition to using |
| 16 | Fossil. |
| 17 | |
| 18 | If you do not wish to submit a Contributor Agreement, we would still |
| 19 | welcome your suggestions and example code, but we will not use your code |
| 20 | directly - we will be forced to reimplement your changes from scratch which |
| 21 | might take longer. |
| 22 | |
| 23 | <h2>2.0 Submitting Patches</h2> |
| 24 | |
| 25 | Suggested changes or bug fixes can be submitted by creating a patch |
| 26 |
| --- www/contribute.wiki | |
| +++ www/contribute.wiki | |
| @@ -15,11 +15,11 @@ | |
| 15 | and other lawyer-rich organizations require this as a precondition to using |
| 16 | Fossil. |
| 17 | |
| 18 | If you do not wish to submit a Contributor Agreement, we would still |
| 19 | welcome your suggestions and example code, but we will not use your code |
| 20 | directly - we will be forced to re-implement your changes from scratch which |
| 21 | might take longer. |
| 22 | |
| 23 | <h2>2.0 Submitting Patches</h2> |
| 24 | |
| 25 | Suggested changes or bug fixes can be submitted by creating a patch |
| 26 |
+1
-1
| --- www/fileformat.wiki | ||
| +++ www/fileformat.wiki | ||
| @@ -317,11 +317,11 @@ | ||
| 317 | 317 | The "*" character means the tag should be added to the artifact |
| 318 | 318 | and all direct descendants (but not descendants through a merge) down |
| 319 | 319 | to but not including the first descendant that contains a |
| 320 | 320 | more recent "-", "*", or "+" tag with the same name. |
| 321 | 321 | The optional third argument is the value of the tag. A tag |
| 322 | -without a value is a boolean. | |
| 322 | +without a value is a Boolean. | |
| 323 | 323 | |
| 324 | 324 | When two or more tags with the same name are applied to the |
| 325 | 325 | same artifact, the tag with the latest (most recent) date is |
| 326 | 326 | used. |
| 327 | 327 | |
| 328 | 328 |
| --- www/fileformat.wiki | |
| +++ www/fileformat.wiki | |
| @@ -317,11 +317,11 @@ | |
| 317 | The "*" character means the tag should be added to the artifact |
| 318 | and all direct descendants (but not descendants through a merge) down |
| 319 | to but not including the first descendant that contains a |
| 320 | more recent "-", "*", or "+" tag with the same name. |
| 321 | The optional third argument is the value of the tag. A tag |
| 322 | without a value is a boolean. |
| 323 | |
| 324 | When two or more tags with the same name are applied to the |
| 325 | same artifact, the tag with the latest (most recent) date is |
| 326 | used. |
| 327 | |
| 328 |
| --- www/fileformat.wiki | |
| +++ www/fileformat.wiki | |
| @@ -317,11 +317,11 @@ | |
| 317 | The "*" character means the tag should be added to the artifact |
| 318 | and all direct descendants (but not descendants through a merge) down |
| 319 | to but not including the first descendant that contains a |
| 320 | more recent "-", "*", or "+" tag with the same name. |
| 321 | The optional third argument is the value of the tag. A tag |
| 322 | without a value is a Boolean. |
| 323 | |
| 324 | When two or more tags with the same name are applied to the |
| 325 | same artifact, the tag with the latest (most recent) date is |
| 326 | used. |
| 327 | |
| 328 |
+5
-5
| --- www/fiveminutes.wiki | ||
| +++ www/fiveminutes.wiki | ||
| @@ -5,18 +5,18 @@ | ||
| 5 | 5 | </i></b> |
| 6 | 6 | </p><hr> |
| 7 | 7 | |
| 8 | 8 | <h1>Up and running in 5 minutes as a single user</h1> |
| 9 | 9 | <p>This short document explains the main basic Fossil commands for a single |
| 10 | -user, ie. with no additional users, with no need to synchronize with some remote | |
| 10 | +user, i.e. with no additional users, with no need to synchronize with some remote | |
| 11 | 11 | repository, and no need for branching/forking.</p> |
| 12 | 12 | |
| 13 | 13 | <h2>Create a new repository</h2> |
| 14 | 14 | <p>fossil new c:\test.repo</p> |
| 15 | -<p>This will create the new SQLite binary file that holds the repository, ie. | |
| 15 | +<p>This will create the new SQLite binary file that holds the repository, i.e. | |
| 16 | 16 | files, tickets, wiki, etc. It can be located anywhere, although it's considered |
| 17 | -best practise to keep it outside the work directory where you will work on files | |
| 17 | +best practice to keep it outside the work directory where you will work on files | |
| 18 | 18 | after they've been checked out of the repository.</p> |
| 19 | 19 | |
| 20 | 20 | <h2>Open the repository</h2> |
| 21 | 21 | <p>cd c:\temp\test.fossil</p> |
| 22 | 22 | <p>fossil open c:\test.repo</p> |
| @@ -27,11 +27,11 @@ | ||
| 27 | 27 | |
| 28 | 28 | <h2>Add new files</h2> |
| 29 | 29 | <p>fossil add .</p> |
| 30 | 30 | <p>To tell Fossil to add new files to the repository. The files aren't actually |
| 31 | 31 | added until you run "commit". When using ".", it tells Fossil |
| 32 | -to add all the files in the current directory recursively, ie. including all | |
| 32 | +to add all the files in the current directory recursively, i.e. including all | |
| 33 | 33 | the files in all the subdirectories.</p> |
| 34 | 34 | <p>Note: To tell Fossil to ignore some extensions:</p> |
| 35 | 35 | <p>fossil settings ignore-glob "*.o,*.obj,*.exe" --global</p> |
| 36 | 36 | |
| 37 | 37 | <h2>Remove files that haven't been committed yet</h2> |
| @@ -44,11 +44,11 @@ | ||
| 44 | 44 | <p>This shows the list of changes that have been done and will be committed the |
| 45 | 45 | next time you run "fossil commit". It's a useful command to run before |
| 46 | 46 | running "fossil commit" just to check that things are OK before proceeding.</p> |
| 47 | 47 | |
| 48 | 48 | <h2>Commit changes</h2> |
| 49 | -<p>To actually apply the pending changes to the repository, eg. new files marked | |
| 49 | +<p>To actually apply the pending changes to the repository, e.g. new files marked | |
| 50 | 50 | for addition, checked-out files that have been edited and must be checked-in, |
| 51 | 51 | etc.</p> |
| 52 | 52 | |
| 53 | 53 | <p>fossil commit -m "Added stuff"</p> |
| 54 | 54 | |
| 55 | 55 |
| --- www/fiveminutes.wiki | |
| +++ www/fiveminutes.wiki | |
| @@ -5,18 +5,18 @@ | |
| 5 | </i></b> |
| 6 | </p><hr> |
| 7 | |
| 8 | <h1>Up and running in 5 minutes as a single user</h1> |
| 9 | <p>This short document explains the main basic Fossil commands for a single |
| 10 | user, ie. with no additional users, with no need to synchronize with some remote |
| 11 | repository, and no need for branching/forking.</p> |
| 12 | |
| 13 | <h2>Create a new repository</h2> |
| 14 | <p>fossil new c:\test.repo</p> |
| 15 | <p>This will create the new SQLite binary file that holds the repository, ie. |
| 16 | files, tickets, wiki, etc. It can be located anywhere, although it's considered |
| 17 | best practise to keep it outside the work directory where you will work on files |
| 18 | after they've been checked out of the repository.</p> |
| 19 | |
| 20 | <h2>Open the repository</h2> |
| 21 | <p>cd c:\temp\test.fossil</p> |
| 22 | <p>fossil open c:\test.repo</p> |
| @@ -27,11 +27,11 @@ | |
| 27 | |
| 28 | <h2>Add new files</h2> |
| 29 | <p>fossil add .</p> |
| 30 | <p>To tell Fossil to add new files to the repository. The files aren't actually |
| 31 | added until you run "commit". When using ".", it tells Fossil |
| 32 | to add all the files in the current directory recursively, ie. including all |
| 33 | the files in all the subdirectories.</p> |
| 34 | <p>Note: To tell Fossil to ignore some extensions:</p> |
| 35 | <p>fossil settings ignore-glob "*.o,*.obj,*.exe" --global</p> |
| 36 | |
| 37 | <h2>Remove files that haven't been committed yet</h2> |
| @@ -44,11 +44,11 @@ | |
| 44 | <p>This shows the list of changes that have been done and will be committed the |
| 45 | next time you run "fossil commit". It's a useful command to run before |
| 46 | running "fossil commit" just to check that things are OK before proceeding.</p> |
| 47 | |
| 48 | <h2>Commit changes</h2> |
| 49 | <p>To actually apply the pending changes to the repository, eg. new files marked |
| 50 | for addition, checked-out files that have been edited and must be checked-in, |
| 51 | etc.</p> |
| 52 | |
| 53 | <p>fossil commit -m "Added stuff"</p> |
| 54 | |
| 55 |
| --- www/fiveminutes.wiki | |
| +++ www/fiveminutes.wiki | |
| @@ -5,18 +5,18 @@ | |
| 5 | </i></b> |
| 6 | </p><hr> |
| 7 | |
| 8 | <h1>Up and running in 5 minutes as a single user</h1> |
| 9 | <p>This short document explains the main basic Fossil commands for a single |
| 10 | user, i.e. with no additional users, with no need to synchronize with some remote |
| 11 | repository, and no need for branching/forking.</p> |
| 12 | |
| 13 | <h2>Create a new repository</h2> |
| 14 | <p>fossil new c:\test.repo</p> |
| 15 | <p>This will create the new SQLite binary file that holds the repository, i.e. |
| 16 | files, tickets, wiki, etc. It can be located anywhere, although it's considered |
| 17 | best practice to keep it outside the work directory where you will work on files |
| 18 | after they've been checked out of the repository.</p> |
| 19 | |
| 20 | <h2>Open the repository</h2> |
| 21 | <p>cd c:\temp\test.fossil</p> |
| 22 | <p>fossil open c:\test.repo</p> |
| @@ -27,11 +27,11 @@ | |
| 27 | |
| 28 | <h2>Add new files</h2> |
| 29 | <p>fossil add .</p> |
| 30 | <p>To tell Fossil to add new files to the repository. The files aren't actually |
| 31 | added until you run "commit". When using ".", it tells Fossil |
| 32 | to add all the files in the current directory recursively, i.e. including all |
| 33 | the files in all the subdirectories.</p> |
| 34 | <p>Note: To tell Fossil to ignore some extensions:</p> |
| 35 | <p>fossil settings ignore-glob "*.o,*.obj,*.exe" --global</p> |
| 36 | |
| 37 | <h2>Remove files that haven't been committed yet</h2> |
| @@ -44,11 +44,11 @@ | |
| 44 | <p>This shows the list of changes that have been done and will be committed the |
| 45 | next time you run "fossil commit". It's a useful command to run before |
| 46 | running "fossil commit" just to check that things are OK before proceeding.</p> |
| 47 | |
| 48 | <h2>Commit changes</h2> |
| 49 | <p>To actually apply the pending changes to the repository, e.g. new files marked |
| 50 | for addition, checked-out files that have been edited and must be checked-in, |
| 51 | etc.</p> |
| 52 | |
| 53 | <p>fossil commit -m "Added stuff"</p> |
| 54 | |
| 55 |
+3
-3
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -57,11 +57,11 @@ | ||
| 57 | 57 | of integrators merge changes from individual developers into collaborative |
| 58 | 58 | branches, until all the changes are merged together at the top-level master |
| 59 | 59 | branch. And all of this can be accomplished without having to have all the |
| 60 | 60 | code in any one repository. Developers or groups of developers can share |
| 61 | 61 | only those branches that they want to share and keep other branches of the |
| 62 | -project private. This is analogous to sharding an a distributed database. | |
| 62 | +project private. This is analogous to sharding a distributed database. | |
| 63 | 63 | |
| 64 | 64 | Fossil allows private branches, but its default mode is to share everything. |
| 65 | 65 | And so in a Fossil project, all repositories tend to contain all of the |
| 66 | 66 | content at all times. This is analogous to replication in a |
| 67 | 67 | distributed database. |
| @@ -76,11 +76,11 @@ | ||
| 76 | 76 | works in his or her own branch and then merges changes up the hierarchy |
| 77 | 77 | until they reach the master branch. |
| 78 | 78 | |
| 79 | 79 | Fossil is designed for smaller and non-hierarchical teams where all |
| 80 | 80 | developers are operating directly on the master branch, or at most |
| 81 | -a small number of well defined branches. | |
| 81 | +a small number of well-defined branches. | |
| 82 | 82 | The [./concepts.wiki#workflow | autosync] mode of Fossil makes it easy |
| 83 | 83 | for multiple developers to work on a single branch and maintain |
| 84 | 84 | linear development on that branch and avoid needless forking |
| 85 | 85 | and merging. |
| 86 | 86 | |
| @@ -115,11 +115,11 @@ | ||
| 115 | 115 | So to a first approximation, branches in Git are developer-centric whereas |
| 116 | 116 | branches in Fossil are feature-centric. |
| 117 | 117 | |
| 118 | 118 | The Git approach scales much better for large projects like the Linux |
| 119 | 119 | kernel with thousands of contributors who in many cases don't even know |
| 120 | -each others names. The integrators serve a gatekeeper role to help keep | |
| 120 | +each other's names. The integrators serve a gatekeeper role to help keep | |
| 121 | 121 | undesirable code out of the official Linux source tree. On the other hand, |
| 122 | 122 | not many projects are as big or as loosely organized as the Linux kernel. |
| 123 | 123 | Most projects have a small team of developers who all know each other |
| 124 | 124 | well and trust each other, and who enjoy working together collaboratively |
| 125 | 125 | without the overhead and hierarchy of integrators. |
| 126 | 126 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -57,11 +57,11 @@ | |
| 57 | of integrators merge changes from individual developers into collaborative |
| 58 | branches, until all the changes are merged together at the top-level master |
| 59 | branch. And all of this can be accomplished without having to have all the |
| 60 | code in any one repository. Developers or groups of developers can share |
| 61 | only those branches that they want to share and keep other branches of the |
| 62 | project private. This is analogous to sharding an a distributed database. |
| 63 | |
| 64 | Fossil allows private branches, but its default mode is to share everything. |
| 65 | And so in a Fossil project, all repositories tend to contain all of the |
| 66 | content at all times. This is analogous to replication in a |
| 67 | distributed database. |
| @@ -76,11 +76,11 @@ | |
| 76 | works in his or her own branch and then merges changes up the hierarchy |
| 77 | until they reach the master branch. |
| 78 | |
| 79 | Fossil is designed for smaller and non-hierarchical teams where all |
| 80 | developers are operating directly on the master branch, or at most |
| 81 | a small number of well defined branches. |
| 82 | The [./concepts.wiki#workflow | autosync] mode of Fossil makes it easy |
| 83 | for multiple developers to work on a single branch and maintain |
| 84 | linear development on that branch and avoid needless forking |
| 85 | and merging. |
| 86 | |
| @@ -115,11 +115,11 @@ | |
| 115 | So to a first approximation, branches in Git are developer-centric whereas |
| 116 | branches in Fossil are feature-centric. |
| 117 | |
| 118 | The Git approach scales much better for large projects like the Linux |
| 119 | kernel with thousands of contributors who in many cases don't even know |
| 120 | each others names. The integrators serve a gatekeeper role to help keep |
| 121 | undesirable code out of the official Linux source tree. On the other hand, |
| 122 | not many projects are as big or as loosely organized as the Linux kernel. |
| 123 | Most projects have a small team of developers who all know each other |
| 124 | well and trust each other, and who enjoy working together collaboratively |
| 125 | without the overhead and hierarchy of integrators. |
| 126 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -57,11 +57,11 @@ | |
| 57 | of integrators merge changes from individual developers into collaborative |
| 58 | branches, until all the changes are merged together at the top-level master |
| 59 | branch. And all of this can be accomplished without having to have all the |
| 60 | code in any one repository. Developers or groups of developers can share |
| 61 | only those branches that they want to share and keep other branches of the |
| 62 | project private. This is analogous to sharding a distributed database. |
| 63 | |
| 64 | Fossil allows private branches, but its default mode is to share everything. |
| 65 | And so in a Fossil project, all repositories tend to contain all of the |
| 66 | content at all times. This is analogous to replication in a |
| 67 | distributed database. |
| @@ -76,11 +76,11 @@ | |
| 76 | works in his or her own branch and then merges changes up the hierarchy |
| 77 | until they reach the master branch. |
| 78 | |
| 79 | Fossil is designed for smaller and non-hierarchical teams where all |
| 80 | developers are operating directly on the master branch, or at most |
| 81 | a small number of well-defined branches. |
| 82 | The [./concepts.wiki#workflow | autosync] mode of Fossil makes it easy |
| 83 | for multiple developers to work on a single branch and maintain |
| 84 | linear development on that branch and avoid needless forking |
| 85 | and merging. |
| 86 | |
| @@ -115,11 +115,11 @@ | |
| 115 | So to a first approximation, branches in Git are developer-centric whereas |
| 116 | branches in Fossil are feature-centric. |
| 117 | |
| 118 | The Git approach scales much better for large projects like the Linux |
| 119 | kernel with thousands of contributors who in many cases don't even know |
| 120 | each other's names. The integrators serve a gatekeeper role to help keep |
| 121 | undesirable code out of the official Linux source tree. On the other hand, |
| 122 | not many projects are as big or as loosely organized as the Linux kernel. |
| 123 | Most projects have a small team of developers who all know each other |
| 124 | well and trust each other, and who enjoy working together collaboratively |
| 125 | without the overhead and hierarchy of integrators. |
| 126 |
+1
-1
| --- www/private.wiki | ||
| +++ www/private.wiki | ||
| @@ -45,11 +45,11 @@ | ||
| 45 | 45 | with another repository. For example, you might be building a cross-platform |
| 46 | 46 | application and have separate repositories on your Windows laptop, |
| 47 | 47 | your Linux desktop, and your iMac. You can transfer private branches |
| 48 | 48 | between these machines by using the --private option on the "sync", |
| 49 | 49 | "push", "pull", and "clone" commands. For example, if you are running |
| 50 | -"fossil server" on your linux box and you want to clone that repository | |
| 50 | +"fossil server" on your Linux box and you want to clone that repository | |
| 51 | 51 | to your Mac, including all private branches, use: |
| 52 | 52 | |
| 53 | 53 | <blockquote><pre> |
| 54 | 54 | fossil clone --private http://[email protected]:8080/ mac-clone.fossil |
| 55 | 55 | </pre></blockquote> |
| 56 | 56 |
| --- www/private.wiki | |
| +++ www/private.wiki | |
| @@ -45,11 +45,11 @@ | |
| 45 | with another repository. For example, you might be building a cross-platform |
| 46 | application and have separate repositories on your Windows laptop, |
| 47 | your Linux desktop, and your iMac. You can transfer private branches |
| 48 | between these machines by using the --private option on the "sync", |
| 49 | "push", "pull", and "clone" commands. For example, if you are running |
| 50 | "fossil server" on your linux box and you want to clone that repository |
| 51 | to your Mac, including all private branches, use: |
| 52 | |
| 53 | <blockquote><pre> |
| 54 | fossil clone --private http://[email protected]:8080/ mac-clone.fossil |
| 55 | </pre></blockquote> |
| 56 |
| --- www/private.wiki | |
| +++ www/private.wiki | |
| @@ -45,11 +45,11 @@ | |
| 45 | with another repository. For example, you might be building a cross-platform |
| 46 | application and have separate repositories on your Windows laptop, |
| 47 | your Linux desktop, and your iMac. You can transfer private branches |
| 48 | between these machines by using the --private option on the "sync", |
| 49 | "push", "pull", and "clone" commands. For example, if you are running |
| 50 | "fossil server" on your Linux box and you want to clone that repository |
| 51 | to your Mac, including all private branches, use: |
| 52 | |
| 53 | <blockquote><pre> |
| 54 | fossil clone --private http://[email protected]:8080/ mac-clone.fossil |
| 55 | </pre></blockquote> |
| 56 |
+2
-2
| --- www/quickstart.wiki | ||
| +++ www/quickstart.wiki | ||
| @@ -76,11 +76,11 @@ | ||
| 76 | 76 | |
| 77 | 77 | <p>A Fossil repository is a single disk file. Instead of cloning, |
| 78 | 78 | you can just make a copy of the repository file (for example, using |
| 79 | 79 | "scp"). Note, however, that the repository file contains auxiliary |
| 80 | 80 | information above and beyond the versioned files, including some |
| 81 | - sensitive information such as password hashs and email addresses. If you | |
| 81 | + sensitive information such as password hashes and email addresses. If you | |
| 82 | 82 | want to share Fossil repositories directly, consider running the |
| 83 | 83 | [/help/scrub|fossil scrub] command to remove sensitive information |
| 84 | 84 | before transmitting the file. |
| 85 | 85 | |
| 86 | 86 | <h2>Importing From Another Version Control System</h2> |
| @@ -336,11 +336,11 @@ | ||
| 336 | 336 | <li>[./server.wiki#inetd|inetd/xinetd] |
| 337 | 337 | <li>[./server.wiki#cgi|CGI] |
| 338 | 338 | <li>[./server.wiki#scgi|SCGI] |
| 339 | 339 | </ul> |
| 340 | 340 | |
| 341 | - <p>The the [./selfhost.wiki | self-hosting fossil repositories] use | |
| 341 | + <p>The [./selfhost.wiki | self-hosting fossil repositories] use | |
| 342 | 342 | CGI. |
| 343 | 343 | |
| 344 | 344 | <a name="proxy"></a> |
| 345 | 345 | <h2>HTTP Proxies</h2> |
| 346 | 346 | |
| 347 | 347 |
| --- www/quickstart.wiki | |
| +++ www/quickstart.wiki | |
| @@ -76,11 +76,11 @@ | |
| 76 | |
| 77 | <p>A Fossil repository is a single disk file. Instead of cloning, |
| 78 | you can just make a copy of the repository file (for example, using |
| 79 | "scp"). Note, however, that the repository file contains auxiliary |
| 80 | information above and beyond the versioned files, including some |
| 81 | sensitive information such as password hashs and email addresses. If you |
| 82 | want to share Fossil repositories directly, consider running the |
| 83 | [/help/scrub|fossil scrub] command to remove sensitive information |
| 84 | before transmitting the file. |
| 85 | |
| 86 | <h2>Importing From Another Version Control System</h2> |
| @@ -336,11 +336,11 @@ | |
| 336 | <li>[./server.wiki#inetd|inetd/xinetd] |
| 337 | <li>[./server.wiki#cgi|CGI] |
| 338 | <li>[./server.wiki#scgi|SCGI] |
| 339 | </ul> |
| 340 | |
| 341 | <p>The the [./selfhost.wiki | self-hosting fossil repositories] use |
| 342 | CGI. |
| 343 | |
| 344 | <a name="proxy"></a> |
| 345 | <h2>HTTP Proxies</h2> |
| 346 | |
| 347 |
| --- www/quickstart.wiki | |
| +++ www/quickstart.wiki | |
| @@ -76,11 +76,11 @@ | |
| 76 | |
| 77 | <p>A Fossil repository is a single disk file. Instead of cloning, |
| 78 | you can just make a copy of the repository file (for example, using |
| 79 | "scp"). Note, however, that the repository file contains auxiliary |
| 80 | information above and beyond the versioned files, including some |
| 81 | sensitive information such as password hashes and email addresses. If you |
| 82 | want to share Fossil repositories directly, consider running the |
| 83 | [/help/scrub|fossil scrub] command to remove sensitive information |
| 84 | before transmitting the file. |
| 85 | |
| 86 | <h2>Importing From Another Version Control System</h2> |
| @@ -336,11 +336,11 @@ | |
| 336 | <li>[./server.wiki#inetd|inetd/xinetd] |
| 337 | <li>[./server.wiki#cgi|CGI] |
| 338 | <li>[./server.wiki#scgi|SCGI] |
| 339 | </ul> |
| 340 | |
| 341 | <p>The [./selfhost.wiki | self-hosting fossil repositories] use |
| 342 | CGI. |
| 343 | |
| 344 | <a name="proxy"></a> |
| 345 | <h2>HTTP Proxies</h2> |
| 346 | |
| 347 |
+2
-2
| --- www/server.wiki | ||
| +++ www/server.wiki | ||
| @@ -111,11 +111,11 @@ | ||
| 111 | 111 | accept = www.ubercool-project.org:443 |
| 112 | 112 | TIMEOUTclose = 0 |
| 113 | 113 | exec = /usr/bin/fossil |
| 114 | 114 | execargs = /usr/bin/fossil http /home/fossil/ubercool.fossil --https |
| 115 | 115 | </nowiki></pre></blockquote> |
| 116 | -See the stunnel4 documentation for further details bout the /etc/stunnel/stunnel.conf | |
| 116 | +See the stunnel4 documentation for further details about the /etc/stunnel/stunnel.conf | |
| 117 | 117 | configuration file. Note that the [/help/http|fossil http] command should include |
| 118 | 118 | the --https option to let Fossil know to use "https" instead of "http" as the scheme |
| 119 | 119 | on generated hyperlinks. |
| 120 | 120 | <p> |
| 121 | 121 | Using inetd or xinetd or stunnel is a more complex setup |
| @@ -313,11 +313,11 @@ | ||
| 313 | 313 | </pre></blockquote> |
| 314 | 314 | The second form is especially useful for changing the maximum load average |
| 315 | 315 | simultaneously on a large number of repositories. |
| 316 | 316 | <p> |
| 317 | 317 | Note that this load-average limiting feature is only available on operating |
| 318 | -systems that support the "getloadavg()" API. Most modern unix systems have | |
| 318 | +systems that support the "getloadavg()" API. Most modern Unix systems have | |
| 319 | 319 | this interface, but Windows does not, so the feature will not work on Windows. |
| 320 | 320 | Note also that Linux implements "getloadavg()" by accessing the "/proc/loadavg" |
| 321 | 321 | file in the "proc" virtual filesystem. If you are running a Fossil instance |
| 322 | 322 | inside a chroot() jail on Linux, you will need to make the "/proc" file |
| 323 | 323 | system available inside that jail in order for this feature to work. On |
| 324 | 324 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -111,11 +111,11 @@ | |
| 111 | accept = www.ubercool-project.org:443 |
| 112 | TIMEOUTclose = 0 |
| 113 | exec = /usr/bin/fossil |
| 114 | execargs = /usr/bin/fossil http /home/fossil/ubercool.fossil --https |
| 115 | </nowiki></pre></blockquote> |
| 116 | See the stunnel4 documentation for further details bout the /etc/stunnel/stunnel.conf |
| 117 | configuration file. Note that the [/help/http|fossil http] command should include |
| 118 | the --https option to let Fossil know to use "https" instead of "http" as the scheme |
| 119 | on generated hyperlinks. |
| 120 | <p> |
| 121 | Using inetd or xinetd or stunnel is a more complex setup |
| @@ -313,11 +313,11 @@ | |
| 313 | </pre></blockquote> |
| 314 | The second form is especially useful for changing the maximum load average |
| 315 | simultaneously on a large number of repositories. |
| 316 | <p> |
| 317 | Note that this load-average limiting feature is only available on operating |
| 318 | systems that support the "getloadavg()" API. Most modern unix systems have |
| 319 | this interface, but Windows does not, so the feature will not work on Windows. |
| 320 | Note also that Linux implements "getloadavg()" by accessing the "/proc/loadavg" |
| 321 | file in the "proc" virtual filesystem. If you are running a Fossil instance |
| 322 | inside a chroot() jail on Linux, you will need to make the "/proc" file |
| 323 | system available inside that jail in order for this feature to work. On |
| 324 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -111,11 +111,11 @@ | |
| 111 | accept = www.ubercool-project.org:443 |
| 112 | TIMEOUTclose = 0 |
| 113 | exec = /usr/bin/fossil |
| 114 | execargs = /usr/bin/fossil http /home/fossil/ubercool.fossil --https |
| 115 | </nowiki></pre></blockquote> |
| 116 | See the stunnel4 documentation for further details about the /etc/stunnel/stunnel.conf |
| 117 | configuration file. Note that the [/help/http|fossil http] command should include |
| 118 | the --https option to let Fossil know to use "https" instead of "http" as the scheme |
| 119 | on generated hyperlinks. |
| 120 | <p> |
| 121 | Using inetd or xinetd or stunnel is a more complex setup |
| @@ -313,11 +313,11 @@ | |
| 313 | </pre></blockquote> |
| 314 | The second form is especially useful for changing the maximum load average |
| 315 | simultaneously on a large number of repositories. |
| 316 | <p> |
| 317 | Note that this load-average limiting feature is only available on operating |
| 318 | systems that support the "getloadavg()" API. Most modern Unix systems have |
| 319 | this interface, but Windows does not, so the feature will not work on Windows. |
| 320 | Note also that Linux implements "getloadavg()" by accessing the "/proc/loadavg" |
| 321 | file in the "proc" virtual filesystem. If you are running a Fossil instance |
| 322 | inside a chroot() jail on Linux, you will need to make the "/proc" file |
| 323 | system available inside that jail in order for this feature to work. On |
| 324 |
+1
-1
| --- www/stats.wiki | ||
| +++ www/stats.wiki | ||
| @@ -152,8 +152,8 @@ | ||
| 152 | 152 | fossil using only about 23.2MB of network traffic. (This 23.2MB includes |
| 153 | 153 | all the changes to SQLite that have been made since the conversion from |
| 154 | 154 | CVS. Of those changes are omitted, the clone bandwidth drops to 13MB.) |
| 155 | 155 | The "sync" protocol |
| 156 | 156 | used by fossil has turned out to be surprisingly efficient. A typical |
| 157 | -check-in on SQLite might use 3 or 4KB of network bandwidth total. Hardly | |
| 157 | +check-in on SQLite might use 3 or 4KB of network bandwidth total, hardly | |
| 158 | 158 | worth measuring. The sync protocol is efficient enough that, once cloned, |
| 159 | 159 | Fossil could easily be used over a dial-up connection. |
| 160 | 160 |
| --- www/stats.wiki | |
| +++ www/stats.wiki | |
| @@ -152,8 +152,8 @@ | |
| 152 | fossil using only about 23.2MB of network traffic. (This 23.2MB includes |
| 153 | all the changes to SQLite that have been made since the conversion from |
| 154 | CVS. Of those changes are omitted, the clone bandwidth drops to 13MB.) |
| 155 | The "sync" protocol |
| 156 | used by fossil has turned out to be surprisingly efficient. A typical |
| 157 | check-in on SQLite might use 3 or 4KB of network bandwidth total. Hardly |
| 158 | worth measuring. The sync protocol is efficient enough that, once cloned, |
| 159 | Fossil could easily be used over a dial-up connection. |
| 160 |
| --- www/stats.wiki | |
| +++ www/stats.wiki | |
| @@ -152,8 +152,8 @@ | |
| 152 | fossil using only about 23.2MB of network traffic. (This 23.2MB includes |
| 153 | all the changes to SQLite that have been made since the conversion from |
| 154 | CVS. Of those changes are omitted, the clone bandwidth drops to 13MB.) |
| 155 | The "sync" protocol |
| 156 | used by fossil has turned out to be surprisingly efficient. A typical |
| 157 | check-in on SQLite might use 3 or 4KB of network bandwidth total, hardly |
| 158 | worth measuring. The sync protocol is efficient enough that, once cloned, |
| 159 | Fossil could easily be used over a dial-up connection. |
| 160 |
+1
-1
| --- www/style.wiki | ||
| +++ www/style.wiki | ||
| @@ -46,11 +46,11 @@ | ||
| 46 | 46 | |
| 47 | 47 | 30. Every function has a header comment describing the purpose and use |
| 48 | 48 | of the function. |
| 49 | 49 | |
| 50 | 50 | 31. Function header comment defines the behavior of the function in |
| 51 | - sufficient detail to allow the function to be reimplemented from | |
| 51 | + sufficient detail to allow the function to be re-implemented from | |
| 52 | 52 | scratch without reference to the original code. |
| 53 | 53 | |
| 54 | 54 | 32. Functions that perform dynamic memory allocation (either directly |
| 55 | 55 | or indirectly via subfunctions) say so in their header comments. |
| 56 | 56 | |
| 57 | 57 |
| --- www/style.wiki | |
| +++ www/style.wiki | |
| @@ -46,11 +46,11 @@ | |
| 46 | |
| 47 | 30. Every function has a header comment describing the purpose and use |
| 48 | of the function. |
| 49 | |
| 50 | 31. Function header comment defines the behavior of the function in |
| 51 | sufficient detail to allow the function to be reimplemented from |
| 52 | scratch without reference to the original code. |
| 53 | |
| 54 | 32. Functions that perform dynamic memory allocation (either directly |
| 55 | or indirectly via subfunctions) say so in their header comments. |
| 56 | |
| 57 |
| --- www/style.wiki | |
| +++ www/style.wiki | |
| @@ -46,11 +46,11 @@ | |
| 46 | |
| 47 | 30. Every function has a header comment describing the purpose and use |
| 48 | of the function. |
| 49 | |
| 50 | 31. Function header comment defines the behavior of the function in |
| 51 | sufficient detail to allow the function to be re-implemented from |
| 52 | scratch without reference to the original code. |
| 53 | |
| 54 | 32. Functions that perform dynamic memory allocation (either directly |
| 55 | or indirectly via subfunctions) say so in their header comments. |
| 56 | |
| 57 |
+1
-1
| --- www/tech_overview.wiki | ||
| +++ www/tech_overview.wiki | ||
| @@ -124,11 +124,11 @@ | ||
| 124 | 124 | |
| 125 | 125 | The configuration database also maintains a list of repositories. This |
| 126 | 126 | list is used by the [/help/all | fossil all] command in order to run various |
| 127 | 127 | operations such as "sync" or "rebuild" on all repositories managed by a user. |
| 128 | 128 | |
| 129 | -On unix systems, the configuration database is named ".fossil" and is | |
| 129 | +On Unix systems, the configuration database is named ".fossil" and is | |
| 130 | 130 | located in the user's home directory. On windows, the configuration |
| 131 | 131 | database is named "_fossil" (using an underscore as the first character |
| 132 | 132 | instead of a dot) and is located in the directory specified by the |
| 133 | 133 | LOCALAPPDATA, APPDATA, or HOMEPATH environment variables, in that order. |
| 134 | 134 | |
| 135 | 135 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -124,11 +124,11 @@ | |
| 124 | |
| 125 | The configuration database also maintains a list of repositories. This |
| 126 | list is used by the [/help/all | fossil all] command in order to run various |
| 127 | operations such as "sync" or "rebuild" on all repositories managed by a user. |
| 128 | |
| 129 | On unix systems, the configuration database is named ".fossil" and is |
| 130 | located in the user's home directory. On windows, the configuration |
| 131 | database is named "_fossil" (using an underscore as the first character |
| 132 | instead of a dot) and is located in the directory specified by the |
| 133 | LOCALAPPDATA, APPDATA, or HOMEPATH environment variables, in that order. |
| 134 | |
| 135 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -124,11 +124,11 @@ | |
| 124 | |
| 125 | The configuration database also maintains a list of repositories. This |
| 126 | list is used by the [/help/all | fossil all] command in order to run various |
| 127 | operations such as "sync" or "rebuild" on all repositories managed by a user. |
| 128 | |
| 129 | On Unix systems, the configuration database is named ".fossil" and is |
| 130 | located in the user's home directory. On windows, the configuration |
| 131 | database is named "_fossil" (using an underscore as the first character |
| 132 | instead of a dot) and is located in the directory specified by the |
| 133 | LOCALAPPDATA, APPDATA, or HOMEPATH environment variables, in that order. |
| 134 | |
| 135 |
+3
-3
| --- www/th1.md | ||
| +++ www/th1.md | ||
| @@ -5,11 +5,11 @@ | ||
| 5 | 5 | content in Fossil. |
| 6 | 6 | |
| 7 | 7 | Origins |
| 8 | 8 | ------- |
| 9 | 9 | |
| 10 | -TH1 began as a minimalist reimplementation of the TCL scripting language. | |
| 10 | +TH1 began as a minimalist re-implementation of the TCL scripting language. | |
| 11 | 11 | There was a need to test the SQLite library on Symbian phones, but at that |
| 12 | 12 | time all of the test cases for SQLite were written in Tcl and Tcl could not |
| 13 | 13 | be easily compiled on the SymbianOS. So TH1 was developed as a cut-down |
| 14 | 14 | version of TCL that would facilitate running the SQLite test scripts on |
| 15 | 15 | SymbianOS. |
| @@ -157,10 +157,10 @@ | ||
| 157 | 157 | |
| 158 | 158 | Each of the commands above is documented by a block comment above their |
| 159 | 159 | implementation in the th_main.c source file. |
| 160 | 160 | |
| 161 | 161 | **To Do:** We would like to have a community volunteer go through and |
| 162 | -copy the documentation for each of these command (with appropriate | |
| 162 | +copy the documentation for each of these commands (with appropriate | |
| 163 | 163 | format changes and spelling and grammar corrections) into subsequent |
| 164 | 164 | sections of this document. It is suggested that the list of extension |
| 165 | 165 | commands be left intact - as a quick reference. But it would be really |
| 166 | -nice to also have the details of each each command does. | |
| 166 | +nice to also have the details of what each command does. | |
| 167 | 167 |
| --- www/th1.md | |
| +++ www/th1.md | |
| @@ -5,11 +5,11 @@ | |
| 5 | content in Fossil. |
| 6 | |
| 7 | Origins |
| 8 | ------- |
| 9 | |
| 10 | TH1 began as a minimalist reimplementation of the TCL scripting language. |
| 11 | There was a need to test the SQLite library on Symbian phones, but at that |
| 12 | time all of the test cases for SQLite were written in Tcl and Tcl could not |
| 13 | be easily compiled on the SymbianOS. So TH1 was developed as a cut-down |
| 14 | version of TCL that would facilitate running the SQLite test scripts on |
| 15 | SymbianOS. |
| @@ -157,10 +157,10 @@ | |
| 157 | |
| 158 | Each of the commands above is documented by a block comment above their |
| 159 | implementation in the th_main.c source file. |
| 160 | |
| 161 | **To Do:** We would like to have a community volunteer go through and |
| 162 | copy the documentation for each of these command (with appropriate |
| 163 | format changes and spelling and grammar corrections) into subsequent |
| 164 | sections of this document. It is suggested that the list of extension |
| 165 | commands be left intact - as a quick reference. But it would be really |
| 166 | nice to also have the details of each each command does. |
| 167 |
| --- www/th1.md | |
| +++ www/th1.md | |
| @@ -5,11 +5,11 @@ | |
| 5 | content in Fossil. |
| 6 | |
| 7 | Origins |
| 8 | ------- |
| 9 | |
| 10 | TH1 began as a minimalist re-implementation of the TCL scripting language. |
| 11 | There was a need to test the SQLite library on Symbian phones, but at that |
| 12 | time all of the test cases for SQLite were written in Tcl and Tcl could not |
| 13 | be easily compiled on the SymbianOS. So TH1 was developed as a cut-down |
| 14 | version of TCL that would facilitate running the SQLite test scripts on |
| 15 | SymbianOS. |
| @@ -157,10 +157,10 @@ | |
| 157 | |
| 158 | Each of the commands above is documented by a block comment above their |
| 159 | implementation in the th_main.c source file. |
| 160 | |
| 161 | **To Do:** We would like to have a community volunteer go through and |
| 162 | copy the documentation for each of these commands (with appropriate |
| 163 | format changes and spelling and grammar corrections) into subsequent |
| 164 | sections of this document. It is suggested that the list of extension |
| 165 | commands be left intact - as a quick reference. But it would be really |
| 166 | nice to also have the details of what each command does. |
| 167 |
+1
-1
| --- www/webui.wiki | ||
| +++ www/webui.wiki | ||
| @@ -109,11 +109,11 @@ | ||
| 109 | 109 | check-in graph by visiting the "Branches" link on the |
| 110 | 110 | menu bar. From those pages you can follow hyperlinks to get additional |
| 111 | 111 | details. These screens allow you to easily keep track of what is going |
| 112 | 112 | on with separate subteams within your project team. |
| 113 | 113 | |
| 114 | -The "Files" link on the menu allows you to browse though the <b>file | |
| 114 | +The "Files" link on the menu allows you to browse through the <b>file | |
| 115 | 115 | hierarchy</b> of the project and to view complete changes histories on |
| 116 | 116 | individual files, with hyperlinks to the check-ins that made those |
| 117 | 117 | changes, and with diffs and annotated diffs between versions. |
| 118 | 118 | |
| 119 | 119 | The web interface supports [./embeddeddoc.wiki | embedded documentation]. |
| 120 | 120 |
| --- www/webui.wiki | |
| +++ www/webui.wiki | |
| @@ -109,11 +109,11 @@ | |
| 109 | check-in graph by visiting the "Branches" link on the |
| 110 | menu bar. From those pages you can follow hyperlinks to get additional |
| 111 | details. These screens allow you to easily keep track of what is going |
| 112 | on with separate subteams within your project team. |
| 113 | |
| 114 | The "Files" link on the menu allows you to browse though the <b>file |
| 115 | hierarchy</b> of the project and to view complete changes histories on |
| 116 | individual files, with hyperlinks to the check-ins that made those |
| 117 | changes, and with diffs and annotated diffs between versions. |
| 118 | |
| 119 | The web interface supports [./embeddeddoc.wiki | embedded documentation]. |
| 120 |
| --- www/webui.wiki | |
| +++ www/webui.wiki | |
| @@ -109,11 +109,11 @@ | |
| 109 | check-in graph by visiting the "Branches" link on the |
| 110 | menu bar. From those pages you can follow hyperlinks to get additional |
| 111 | details. These screens allow you to easily keep track of what is going |
| 112 | on with separate subteams within your project team. |
| 113 | |
| 114 | The "Files" link on the menu allows you to browse through the <b>file |
| 115 | hierarchy</b> of the project and to view complete changes histories on |
| 116 | individual files, with hyperlinks to the check-ins that made those |
| 117 | changes, and with diffs and annotated diffs between versions. |
| 118 | |
| 119 | The web interface supports [./embeddeddoc.wiki | embedded documentation]. |
| 120 |