Fossil SCM
Minor edits to the Questions and Criticisms document.
Commit
5cbfe0cde22ca9dc41cb0a3fa05d20b8e79d3f7e
Parent
cbc8983685d6ebb…
1 file changed
+15
-13
+15
-13
| --- www/qandc.wiki | ||
| +++ www/qandc.wiki | ||
| @@ -6,17 +6,17 @@ | ||
| 6 | 6 | |
| 7 | 7 | <b>Fossil sounds like a lot of reinvention of the wheel. |
| 8 | 8 | Why create your own DVCS when you could have reused mercurial?</b> |
| 9 | 9 | |
| 10 | 10 | <blockquote> |
| 11 | - I wrote it because none of the | |
| 11 | + <p>I wrote fossil because none of the | |
| 12 | 12 | other available DVCSes met my needs. If the other DVCSes do |
| 13 | - meet your needs, then you probably do not need fossil. But they | |
| 14 | - don't meet mine, and so fossil is necessary for me. | |
| 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 | 15 | |
| 16 | - Feature provided by fossil that one does not get with other | |
| 17 | - DVCSes: | |
| 16 | + <p>Feature provided by fossil that one does not get with other | |
| 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> |
| @@ -69,11 +69,11 @@ | ||
| 69 | 69 | enduring, and simple DVCS than one that looks pretty.</p> |
| 70 | 70 | |
| 71 | 71 | <p>On the other hand, if you have patches that improve the apparance |
| 72 | 72 | of Fossil without seriously compromising its reliablity, performance, |
| 73 | 73 | an maintainability, I will be happy to accept them. Fossil is |
| 74 | -self-hosting. Write to the maintainers for a password that will let | |
| 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 | 79 | keeps the bug-tracking database in a versioned filed. That file can |
| @@ -86,11 +86,11 @@ | ||
| 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 | -I did not know that. Perhaps they choose the name for the same reason that | |
| 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 | 93 | and 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 |
| @@ -112,18 +112,20 @@ | ||
| 112 | 112 | Subversion or Bazaar.</b> |
| 113 | 113 | |
| 114 | 114 | <blockquote> |
| 115 | 115 | <p>I have no doubt that Trac has many features that fossil lacks. But that |
| 116 | 116 | is not the point. Fossil has several key features that Trac lacks and that |
| 117 | -the primary fossil author cannot live without: most notably the fact that | |
| 117 | +I cannot live without: most notably the fact that | |
| 118 | 118 | fossil supports disconnected operation.</p> |
| 119 | 119 | |
| 120 | -<p>As for bloat: Fossil is a single fully self-contained executable. | |
| 121 | -You do not need any external packages in order to run fossil. You do not | |
| 122 | -need diff, patch, merge, cvs, svn, rcs, python, perl, tcl, sqlite, or anything | |
| 123 | -else in order to run fossil. Fossil runs just fine in a chroot jail all | |
| 124 | -by itself. And the self-contained executable is much less than 1MB in size. | |
| 120 | +<p>As for bloat: Fossil is a single self-contained executable. | |
| 121 | +You do not need any other packages | |
| 122 | +(diff, patch, merge, cvs, svn, rcs, git, python, perl, tcl, apache, | |
| 123 | +sqlite, and so forth) | |
| 124 | +in order to run fossil. Fossil runs just fine in a chroot jail all | |
| 125 | +by itself. And the self-contained fossil | |
| 126 | +executable is much less than 1MB in size. | |
| 125 | 127 | Fossil is the very opposite of bloat.</p> |
| 126 | 128 | </blockquote> |
| 127 | 129 | |
| 128 | 130 | |
| 129 | 131 | </nowiki> |
| 130 | 132 |
| --- www/qandc.wiki | |
| +++ www/qandc.wiki | |
| @@ -6,17 +6,17 @@ | |
| 6 | |
| 7 | <b>Fossil sounds like a lot of reinvention of the wheel. |
| 8 | Why create your own DVCS when you could have reused mercurial?</b> |
| 9 | |
| 10 | <blockquote> |
| 11 | I wrote it because none of the |
| 12 | other available DVCSes met my needs. If the other DVCSes do |
| 13 | meet your needs, then you probably do not need fossil. But they |
| 14 | don't meet mine, and so fossil is necessary for me. |
| 15 | |
| 16 | Feature provided by fossil that one does not get with other |
| 17 | DVCSes: |
| 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> |
| @@ -69,11 +69,11 @@ | |
| 69 | enduring, and simple DVCS than one that looks pretty.</p> |
| 70 | |
| 71 | <p>On the other hand, if you have patches that improve the apparance |
| 72 | of Fossil without seriously compromising its reliablity, performance, |
| 73 | an maintainability, I will be happy to accept them. Fossil is |
| 74 | self-hosting. Write to the maintainers for 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 |
| @@ -86,11 +86,11 @@ | |
| 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 choose 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 |
| @@ -112,18 +112,20 @@ | |
| 112 | Subversion or Bazaar.</b> |
| 113 | |
| 114 | <blockquote> |
| 115 | <p>I have no doubt that Trac has many features that fossil lacks. But that |
| 116 | is not the point. Fossil has several key features that Trac lacks and that |
| 117 | the primary fossil author cannot live without: most notably the fact that |
| 118 | fossil supports disconnected operation.</p> |
| 119 | |
| 120 | <p>As for bloat: Fossil is a single fully self-contained executable. |
| 121 | You do not need any external packages in order to run fossil. You do not |
| 122 | need diff, patch, merge, cvs, svn, rcs, python, perl, tcl, sqlite, or anything |
| 123 | else in order to run fossil. Fossil runs just fine in a chroot jail all |
| 124 | by itself. And the self-contained executable is much less than 1MB in size. |
| 125 | Fossil is the very opposite of bloat.</p> |
| 126 | </blockquote> |
| 127 | |
| 128 | |
| 129 | </nowiki> |
| 130 |
| --- www/qandc.wiki | |
| +++ www/qandc.wiki | |
| @@ -6,17 +6,17 @@ | |
| 6 | |
| 7 | <b>Fossil sounds like a lot of reinvention of the wheel. |
| 8 | Why create your own DVCS when you could have reused mercurial?</b> |
| 9 | |
| 10 | <blockquote> |
| 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> |
| @@ -69,11 +69,11 @@ | |
| 69 | enduring, and simple DVCS than one that looks pretty.</p> |
| 70 | |
| 71 | <p>On the other hand, if you have patches that improve the apparance |
| 72 | of Fossil without seriously compromising its reliablity, performance, |
| 73 | an maintainability, I will be happy to accept them. Fossil is |
| 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 |
| @@ -86,11 +86,11 @@ | |
| 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 |
| @@ -112,18 +112,20 @@ | |
| 112 | Subversion or Bazaar.</b> |
| 113 | |
| 114 | <blockquote> |
| 115 | <p>I have no doubt that Trac has many features that fossil lacks. But that |
| 116 | is not the point. Fossil has several key features that Trac lacks and that |
| 117 | I cannot live without: most notably the fact that |
| 118 | fossil supports disconnected operation.</p> |
| 119 | |
| 120 | <p>As for bloat: Fossil is a single self-contained executable. |
| 121 | You do not need any other packages |
| 122 | (diff, patch, merge, cvs, svn, rcs, git, python, perl, tcl, apache, |
| 123 | sqlite, and so forth) |
| 124 | in order to run fossil. Fossil runs just fine in a chroot jail all |
| 125 | by itself. And the self-contained fossil |
| 126 | executable is much less than 1MB in size. |
| 127 | Fossil is the very opposite of bloat.</p> |
| 128 | </blockquote> |
| 129 | |
| 130 | |
| 131 | </nowiki> |
| 132 |