Fossil SCM
Fixed a number of small typos.
Commit
d0e8e88d546eda1fcc18f9401a3f3bc8f4e80777
Parent
3d62a9fb39579b5…
1 file changed
+8
-8
+8
-8
| --- www/qandc.wiki | ||
| +++ www/qandc.wiki | ||
| @@ -11,19 +11,19 @@ | ||
| 11 | 11 | <p>I wrote fossil because none of the |
| 12 | 12 | other available DVCSes met my needs. If the other DVCSes do |
| 13 | 13 | meet your needs, then you might not need fossil. But they |
| 14 | 14 | don't meet mine, and so fossil is necessary for me.</p> |
| 15 | 15 | |
| 16 | - <p>Feature provided by fossil that one does not get with other | |
| 16 | + <p>Features provided by fossil that one does not get with other | |
| 17 | 17 | DVCSes include:</p> |
| 18 | 18 | |
| 19 | 19 | <ol> |
| 20 | 20 | <li> Integrated <a href="wikitheory.wiki">wiki</a>. </li> |
| 21 | 21 | <li> Integrated <a href="bugtheory.wiki">bug tracking</a> </li> |
| 22 | 22 | <li> Immutable artifacts </li> |
| 23 | - <li> self-contained, stand-alone executable </li> | |
| 24 | - <li> simple, well-defined, | |
| 23 | + <li> Self-contained, stand-alone executable </li> | |
| 24 | + <li> Simple, well-defined, | |
| 25 | 25 | <a href="fileformat.wiki">enduring file format</a> </li> |
| 26 | 26 | </ol> |
| 27 | 27 | </blockquote> |
| 28 | 28 | |
| 29 | 29 | <b>Why should I use this rather than Trac?</b> |
| @@ -55,11 +55,11 @@ | ||
| 55 | 55 | The documentation files for |
| 56 | 56 | <a href="http://www.sqlite.org/">SQLite</a> are hosted in a |
| 57 | 57 | fossil repository <a href="http://www.sqlite.org/docsrc/">here</a>, |
| 58 | 58 | for example. |
| 59 | 59 | Other projects are also adopting fossil. But fossil does not yet have |
| 60 | -the massive user base of git or mecurial. | |
| 60 | +the massive user base of git or mercurial. | |
| 61 | 61 | </blockquote> |
| 62 | 62 | |
| 63 | 63 | <b>Fossil looks like the bug tracker that would be in your |
| 64 | 64 | Linksys Router's administration screen.</p> |
| 65 | 65 | |
| @@ -74,25 +74,25 @@ | ||
| 74 | 74 | self-hosting. Send me email to request a password that will let |
| 75 | 75 | you push to the main fossil repository.</p> |
| 76 | 76 | </blockquote> |
| 77 | 77 | |
| 78 | 78 | <b>It would be useful to have a separate application that |
| 79 | -keeps the bug-tracking database in a versioned filed. That file can | |
| 79 | +keeps the bug-tracking database in a versioned file. That file can | |
| 80 | 80 | then be pushed and pulled along with the rest repository.</b> |
| 81 | 81 | |
| 82 | 82 | <blockquote> |
| 83 | -<p>This addressed in the opening paragraphs of | |
| 83 | +<p>This is addressed in the opening paragraphs of | |
| 84 | 84 | the <a href="bugtheory.wiki">Bug-Tracking In Fossil</a> document. |
| 85 | 85 | </blockquote> |
| 86 | 86 | |
| 87 | 87 | <b>Fossil is already the name of a plan9 versioned |
| 88 | 88 | append-only filesystem.</b> |
| 89 | 89 | |
| 90 | 90 | <blockquote> |
| 91 | 91 | I did not know that. Perhaps they selected the name for the same reason that |
| 92 | 92 | I did: because a repository with immutable artifacts preserves |
| 93 | -and excellent fossil record of a long-running project. | |
| 93 | +an excellent fossil record of a long-running project. | |
| 94 | 94 | </blockquote> |
| 95 | 95 | |
| 96 | 96 | <b>The idea of storing a repository in a binary blob like an |
| 97 | 97 | SQLite database terrifies me.</b> |
| 98 | 98 | |
| @@ -99,11 +99,11 @@ | ||
| 99 | 99 | <blockquote> |
| 100 | 100 | The use of SQLite to store the database is likely more stable and secure |
| 101 | 101 | than any other approach, due to the fact that SQLite is transactional. |
| 102 | 102 | Fossil also implements several internal |
| 103 | 103 | <a href="selfcheck.wiki">self-checks</a> to insure that no information |
| 104 | -is every lost. And, indeed, in over a year of operation, there have been | |
| 104 | +is ever lost. And, indeed, in over a year of operation, there have been | |
| 105 | 105 | no reports of data loss due to a Fossil malfunction. |
| 106 | 106 | </blockquote> |
| 107 | 107 | |
| 108 | 108 | |
| 109 | 109 | <b>I am dubious of the benefits of including wikis and bug trackers |
| 110 | 110 |
| --- www/qandc.wiki | |
| +++ www/qandc.wiki | |
| @@ -11,19 +11,19 @@ | |
| 11 | <p>I wrote fossil because none of the |
| 12 | other available DVCSes met my needs. If the other DVCSes do |
| 13 | meet your needs, then you might not need fossil. But they |
| 14 | don't meet mine, and so fossil is necessary for me.</p> |
| 15 | |
| 16 | <p>Feature provided by fossil that one does not get with other |
| 17 | DVCSes include:</p> |
| 18 | |
| 19 | <ol> |
| 20 | <li> Integrated <a href="wikitheory.wiki">wiki</a>. </li> |
| 21 | <li> Integrated <a href="bugtheory.wiki">bug tracking</a> </li> |
| 22 | <li> Immutable artifacts </li> |
| 23 | <li> self-contained, stand-alone executable </li> |
| 24 | <li> simple, well-defined, |
| 25 | <a href="fileformat.wiki">enduring file format</a> </li> |
| 26 | </ol> |
| 27 | </blockquote> |
| 28 | |
| 29 | <b>Why should I use this rather than Trac?</b> |
| @@ -55,11 +55,11 @@ | |
| 55 | The documentation files for |
| 56 | <a href="http://www.sqlite.org/">SQLite</a> are hosted in a |
| 57 | fossil repository <a href="http://www.sqlite.org/docsrc/">here</a>, |
| 58 | for example. |
| 59 | Other projects are also adopting fossil. But fossil does not yet have |
| 60 | the massive user base of git or mecurial. |
| 61 | </blockquote> |
| 62 | |
| 63 | <b>Fossil looks like the bug tracker that would be in your |
| 64 | Linksys Router's administration screen.</p> |
| 65 | |
| @@ -74,25 +74,25 @@ | |
| 74 | self-hosting. Send me email to request a password that will let |
| 75 | you push to the main fossil repository.</p> |
| 76 | </blockquote> |
| 77 | |
| 78 | <b>It would be useful to have a separate application that |
| 79 | keeps the bug-tracking database in a versioned filed. That file can |
| 80 | then be pushed and pulled along with the rest repository.</b> |
| 81 | |
| 82 | <blockquote> |
| 83 | <p>This addressed in the opening paragraphs of |
| 84 | the <a href="bugtheory.wiki">Bug-Tracking In Fossil</a> document. |
| 85 | </blockquote> |
| 86 | |
| 87 | <b>Fossil is already the name of a plan9 versioned |
| 88 | append-only filesystem.</b> |
| 89 | |
| 90 | <blockquote> |
| 91 | I did not know that. Perhaps they selected the name for the same reason that |
| 92 | I did: because a repository with immutable artifacts preserves |
| 93 | and excellent fossil record of a long-running project. |
| 94 | </blockquote> |
| 95 | |
| 96 | <b>The idea of storing a repository in a binary blob like an |
| 97 | SQLite database terrifies me.</b> |
| 98 | |
| @@ -99,11 +99,11 @@ | |
| 99 | <blockquote> |
| 100 | The use of SQLite to store the database is likely more stable and secure |
| 101 | than any other approach, due to the fact that SQLite is transactional. |
| 102 | Fossil also implements several internal |
| 103 | <a href="selfcheck.wiki">self-checks</a> to insure that no information |
| 104 | is every lost. And, indeed, in over a year of operation, there have been |
| 105 | no reports of data loss due to a Fossil malfunction. |
| 106 | </blockquote> |
| 107 | |
| 108 | |
| 109 | <b>I am dubious of the benefits of including wikis and bug trackers |
| 110 |
| --- www/qandc.wiki | |
| +++ www/qandc.wiki | |
| @@ -11,19 +11,19 @@ | |
| 11 | <p>I wrote fossil because none of the |
| 12 | other available DVCSes met my needs. If the other DVCSes do |
| 13 | meet your needs, then you might not need fossil. But they |
| 14 | don't meet mine, and so fossil is necessary for me.</p> |
| 15 | |
| 16 | <p>Features provided by fossil that one does not get with other |
| 17 | DVCSes include:</p> |
| 18 | |
| 19 | <ol> |
| 20 | <li> Integrated <a href="wikitheory.wiki">wiki</a>. </li> |
| 21 | <li> Integrated <a href="bugtheory.wiki">bug tracking</a> </li> |
| 22 | <li> Immutable artifacts </li> |
| 23 | <li> Self-contained, stand-alone executable </li> |
| 24 | <li> Simple, well-defined, |
| 25 | <a href="fileformat.wiki">enduring file format</a> </li> |
| 26 | </ol> |
| 27 | </blockquote> |
| 28 | |
| 29 | <b>Why should I use this rather than Trac?</b> |
| @@ -55,11 +55,11 @@ | |
| 55 | The documentation files for |
| 56 | <a href="http://www.sqlite.org/">SQLite</a> are hosted in a |
| 57 | fossil repository <a href="http://www.sqlite.org/docsrc/">here</a>, |
| 58 | for example. |
| 59 | Other projects are also adopting fossil. But fossil does not yet have |
| 60 | the massive user base of git or mercurial. |
| 61 | </blockquote> |
| 62 | |
| 63 | <b>Fossil looks like the bug tracker that would be in your |
| 64 | Linksys Router's administration screen.</p> |
| 65 | |
| @@ -74,25 +74,25 @@ | |
| 74 | self-hosting. Send me email to request a password that will let |
| 75 | you push to the main fossil repository.</p> |
| 76 | </blockquote> |
| 77 | |
| 78 | <b>It would be useful to have a separate application that |
| 79 | keeps the bug-tracking database in a versioned file. That file can |
| 80 | then be pushed and pulled along with the rest repository.</b> |
| 81 | |
| 82 | <blockquote> |
| 83 | <p>This is addressed in the opening paragraphs of |
| 84 | the <a href="bugtheory.wiki">Bug-Tracking In Fossil</a> document. |
| 85 | </blockquote> |
| 86 | |
| 87 | <b>Fossil is already the name of a plan9 versioned |
| 88 | append-only filesystem.</b> |
| 89 | |
| 90 | <blockquote> |
| 91 | I did not know that. Perhaps they selected the name for the same reason that |
| 92 | I did: because a repository with immutable artifacts preserves |
| 93 | an excellent fossil record of a long-running project. |
| 94 | </blockquote> |
| 95 | |
| 96 | <b>The idea of storing a repository in a binary blob like an |
| 97 | SQLite database terrifies me.</b> |
| 98 | |
| @@ -99,11 +99,11 @@ | |
| 99 | <blockquote> |
| 100 | The use of SQLite to store the database is likely more stable and secure |
| 101 | than any other approach, due to the fact that SQLite is transactional. |
| 102 | Fossil also implements several internal |
| 103 | <a href="selfcheck.wiki">self-checks</a> to insure that no information |
| 104 | is ever lost. And, indeed, in over a year of operation, there have been |
| 105 | no reports of data loss due to a Fossil malfunction. |
| 106 | </blockquote> |
| 107 | |
| 108 | |
| 109 | <b>I am dubious of the benefits of including wikis and bug trackers |
| 110 |