Fossil SCM
Minor wording tweaks to various documentation files.
Commit
5aa71f59b709ae09c108a0e5049bfd997944c9e77058f9596e937baea35453f2
Parent
a54732919d8ed1b…
3 files changed
+2
-2
+3
-3
+1
+2
-2
| --- www/history.md | ||
| +++ www/history.md | ||
| @@ -25,11 +25,11 @@ | ||
| 25 | 25 | |
| 26 | 26 | [300]: https://en.wikipedia.org/wiki/Concurrent_Versions_System |
| 27 | 27 | |
| 28 | 28 | Though innovative and much loved in its time, CVS was not without problems. |
| 29 | 29 | Among those was a lack of visibility into the project history and the |
| 30 | -lack of integrated bug tracking. To try to address these deficiencies, | |
| 30 | +lack of integrated bug tracking. To address these deficiencies, | |
| 31 | 31 | the SQLite author developed the [CVSTrac][305] wrapper for CVS beginning |
| 32 | 32 | in [2002][310]. |
| 33 | 33 | |
| 34 | 34 | [305]: http://cvstrac.org/ |
| 35 | 35 | [310]: http://cvstrac.org/fossil/timeline?a=19700101&n1=10 |
| @@ -65,11 +65,11 @@ | ||
| 65 | 65 | for SQLite began to become evident. The SQLite architect looked |
| 66 | 66 | around for a suitable replacement. Monotone, Git, and Mercurial were |
| 67 | 67 | all considered. But at that time, none of these supported sync |
| 68 | 68 | over ordinary HTTP, none could be run from an inexpensive shell |
| 69 | 69 | account on a leased server (this was before the widespread availability |
| 70 | -of affordable virtual machines), and none of them supported anything | |
| 70 | +of affordable virtual private servers), and none of them supported anything | |
| 71 | 71 | resembling the wiki and ticket features of CVSTrac that had been |
| 72 | 72 | found to be so useful. And so, the SQLite architect began writing |
| 73 | 73 | his own DVCS. |
| 74 | 74 | |
| 75 | 75 | Early prototypes were done in [TCL][340]. As experiments proceeded, |
| 76 | 76 |
| --- www/history.md | |
| +++ www/history.md | |
| @@ -25,11 +25,11 @@ | |
| 25 | |
| 26 | [300]: https://en.wikipedia.org/wiki/Concurrent_Versions_System |
| 27 | |
| 28 | Though innovative and much loved in its time, CVS was not without problems. |
| 29 | Among those was a lack of visibility into the project history and the |
| 30 | lack of integrated bug tracking. To try to address these deficiencies, |
| 31 | the SQLite author developed the [CVSTrac][305] wrapper for CVS beginning |
| 32 | in [2002][310]. |
| 33 | |
| 34 | [305]: http://cvstrac.org/ |
| 35 | [310]: http://cvstrac.org/fossil/timeline?a=19700101&n1=10 |
| @@ -65,11 +65,11 @@ | |
| 65 | for SQLite began to become evident. The SQLite architect looked |
| 66 | around for a suitable replacement. Monotone, Git, and Mercurial were |
| 67 | all considered. But at that time, none of these supported sync |
| 68 | over ordinary HTTP, none could be run from an inexpensive shell |
| 69 | account on a leased server (this was before the widespread availability |
| 70 | of affordable virtual machines), and none of them supported anything |
| 71 | resembling the wiki and ticket features of CVSTrac that had been |
| 72 | found to be so useful. And so, the SQLite architect began writing |
| 73 | his own DVCS. |
| 74 | |
| 75 | Early prototypes were done in [TCL][340]. As experiments proceeded, |
| 76 |
| --- www/history.md | |
| +++ www/history.md | |
| @@ -25,11 +25,11 @@ | |
| 25 | |
| 26 | [300]: https://en.wikipedia.org/wiki/Concurrent_Versions_System |
| 27 | |
| 28 | Though innovative and much loved in its time, CVS was not without problems. |
| 29 | Among those was a lack of visibility into the project history and the |
| 30 | lack of integrated bug tracking. To address these deficiencies, |
| 31 | the SQLite author developed the [CVSTrac][305] wrapper for CVS beginning |
| 32 | in [2002][310]. |
| 33 | |
| 34 | [305]: http://cvstrac.org/ |
| 35 | [310]: http://cvstrac.org/fossil/timeline?a=19700101&n1=10 |
| @@ -65,11 +65,11 @@ | |
| 65 | for SQLite began to become evident. The SQLite architect looked |
| 66 | around for a suitable replacement. Monotone, Git, and Mercurial were |
| 67 | all considered. But at that time, none of these supported sync |
| 68 | over ordinary HTTP, none could be run from an inexpensive shell |
| 69 | account on a leased server (this was before the widespread availability |
| 70 | of affordable virtual private servers), and none of them supported anything |
| 71 | resembling the wiki and ticket features of CVSTrac that had been |
| 72 | found to be so useful. And so, the SQLite architect began writing |
| 73 | his own DVCS. |
| 74 | |
| 75 | Early prototypes were done in [TCL][340]. As experiments proceeded, |
| 76 |
+3
-3
| --- www/index.wiki | ||
| +++ www/index.wiki | ||
| @@ -20,11 +20,11 @@ | ||
| 20 | 20 | </div> |
| 21 | 21 | |
| 22 | 22 | <p>Fossil is a simple, high-reliability, distributed software configuration |
| 23 | 23 | management system with these advanced features: |
| 24 | 24 | |
| 25 | - 1. <b>Integrated Project Management</b> - | |
| 25 | + 1. <b>Project Management</b> - | |
| 26 | 26 | In addition to doing [./concepts.wiki | distributed version control] |
| 27 | 27 | like Git and Mercurial, |
| 28 | 28 | Fossil also supports [./bugtheory.wiki | bug tracking], |
| 29 | 29 | [./wikitheory.wiki | wiki], [./forum.wiki | forum], [./chat.md | chat], and |
| 30 | 30 | [./event.wiki | technotes]. |
| @@ -44,12 +44,12 @@ | ||
| 44 | 44 | [./unvers.wiki | unversioned files]. |
| 45 | 45 | When you clone Fossil from one of its |
| 46 | 46 | [./selfhost.wiki | self-hosting repositories], |
| 47 | 47 | you get more than just source code - you get this entire website. |
| 48 | 48 | |
| 49 | - 3. <b>Self-Contained</b> - | |
| 50 | - Fossil is a single stand-alone executable. | |
| 49 | + 3. <b>All-in-one</b> - | |
| 50 | + Fossil is a single self-contained, stand-alone executable. | |
| 51 | 51 | To install, simply download a |
| 52 | 52 | [/uv/download.html | precompiled binary] |
| 53 | 53 | for Linux, Mac, or Windows and put it on your $PATH. |
| 54 | 54 | [./build.wiki | Easy-to-compile source code] is also available. |
| 55 | 55 | |
| 56 | 56 |
| --- www/index.wiki | |
| +++ www/index.wiki | |
| @@ -20,11 +20,11 @@ | |
| 20 | </div> |
| 21 | |
| 22 | <p>Fossil is a simple, high-reliability, distributed software configuration |
| 23 | management system with these advanced features: |
| 24 | |
| 25 | 1. <b>Integrated Project Management</b> - |
| 26 | In addition to doing [./concepts.wiki | distributed version control] |
| 27 | like Git and Mercurial, |
| 28 | Fossil also supports [./bugtheory.wiki | bug tracking], |
| 29 | [./wikitheory.wiki | wiki], [./forum.wiki | forum], [./chat.md | chat], and |
| 30 | [./event.wiki | technotes]. |
| @@ -44,12 +44,12 @@ | |
| 44 | [./unvers.wiki | unversioned files]. |
| 45 | When you clone Fossil from one of its |
| 46 | [./selfhost.wiki | self-hosting repositories], |
| 47 | you get more than just source code - you get this entire website. |
| 48 | |
| 49 | 3. <b>Self-Contained</b> - |
| 50 | Fossil is a single stand-alone executable. |
| 51 | To install, simply download a |
| 52 | [/uv/download.html | precompiled binary] |
| 53 | for Linux, Mac, or Windows and put it on your $PATH. |
| 54 | [./build.wiki | Easy-to-compile source code] is also available. |
| 55 | |
| 56 |
| --- www/index.wiki | |
| +++ www/index.wiki | |
| @@ -20,11 +20,11 @@ | |
| 20 | </div> |
| 21 | |
| 22 | <p>Fossil is a simple, high-reliability, distributed software configuration |
| 23 | management system with these advanced features: |
| 24 | |
| 25 | 1. <b>Project Management</b> - |
| 26 | In addition to doing [./concepts.wiki | distributed version control] |
| 27 | like Git and Mercurial, |
| 28 | Fossil also supports [./bugtheory.wiki | bug tracking], |
| 29 | [./wikitheory.wiki | wiki], [./forum.wiki | forum], [./chat.md | chat], and |
| 30 | [./event.wiki | technotes]. |
| @@ -44,12 +44,12 @@ | |
| 44 | [./unvers.wiki | unversioned files]. |
| 45 | When you clone Fossil from one of its |
| 46 | [./selfhost.wiki | self-hosting repositories], |
| 47 | you get more than just source code - you get this entire website. |
| 48 | |
| 49 | 3. <b>All-in-one</b> - |
| 50 | Fossil is a single self-contained, stand-alone executable. |
| 51 | To install, simply download a |
| 52 | [/uv/download.html | precompiled binary] |
| 53 | for Linux, Mac, or Windows and put it on your $PATH. |
| 54 | [./build.wiki | Easy-to-compile source code] is also available. |
| 55 | |
| 56 |
+1
| --- www/webui.wiki | ||
| +++ www/webui.wiki | ||
| @@ -7,10 +7,11 @@ | ||
| 7 | 7 | * [./bugtheory.wiki | Ticketing and bug tracking] |
| 8 | 8 | * [./wikitheory.wiki | Wiki] |
| 9 | 9 | * [./embeddeddoc.wiki | On-line documentation] |
| 10 | 10 | * [./event.wiki | Technical notes] |
| 11 | 11 | * [./forum.wiki | Forum] |
| 12 | + * [./chat.md | Chatroom] | |
| 12 | 13 | * Timelines |
| 13 | 14 | * Full text search over all of the above |
| 14 | 15 | * Status information |
| 15 | 16 | * Graphs of revision and branching history |
| 16 | 17 | * File and version lists and differences |
| 17 | 18 |
| --- www/webui.wiki | |
| +++ www/webui.wiki | |
| @@ -7,10 +7,11 @@ | |
| 7 | * [./bugtheory.wiki | Ticketing and bug tracking] |
| 8 | * [./wikitheory.wiki | Wiki] |
| 9 | * [./embeddeddoc.wiki | On-line documentation] |
| 10 | * [./event.wiki | Technical notes] |
| 11 | * [./forum.wiki | Forum] |
| 12 | * Timelines |
| 13 | * Full text search over all of the above |
| 14 | * Status information |
| 15 | * Graphs of revision and branching history |
| 16 | * File and version lists and differences |
| 17 |
| --- www/webui.wiki | |
| +++ www/webui.wiki | |
| @@ -7,10 +7,11 @@ | |
| 7 | * [./bugtheory.wiki | Ticketing and bug tracking] |
| 8 | * [./wikitheory.wiki | Wiki] |
| 9 | * [./embeddeddoc.wiki | On-line documentation] |
| 10 | * [./event.wiki | Technical notes] |
| 11 | * [./forum.wiki | Forum] |
| 12 | * [./chat.md | Chatroom] |
| 13 | * Timelines |
| 14 | * Full text search over all of the above |
| 15 | * Status information |
| 16 | * Graphs of revision and branching history |
| 17 | * File and version lists and differences |
| 18 |