SHA1 Hash:	5cbfe0cde22ca9dc41cb0a3fa05d20b8e79d3f7e
Date:	2008-10-06 11:28:32
User:	drh
Comment:	Minor edits to the Questions and Criticisms document.
Timelines:	ancestors | descendants | both | trunk
Other Links:	files | ZIP archive | manifest

• branch=trunk inherited from [a28c83647d]
• sym-trunk inherited from [a28c83647d]

Modified www/qandc.wiki from [bd20a9934c] to [75989d6590].

@@ -6,17 +6,17 @@
 
 <b>Fossil sounds like a lot of reinvention of the wheel.
 Why create your own DVCS when you could have reused mercurial?</b>
 
 <blockquote>
-  I wrote it because none of the
+  <p>I wrote fossil because none of the
   other available DVCSes met my needs.  If the other DVCSes do
-  meet your needs, then you probably do not need fossil.  But they
-  don't meet mine, and so fossil is necessary for me.
-
-  Feature provided by fossil that one does not get with other
-  DVCSes:
+  meet your needs, then you might not need fossil.  But they
+  don't meet mine, and so fossil is necessary for me.</p>
+
+  <p>Feature provided by fossil that one does not get with other
+  DVCSes include:</p>
 
   <ol>
   <li> Integrated <a href="wikitheory.wiki">wiki</a>. </li>
   <li> Integrated <a href="bugtheory.wiki">bug tracking</a> </li>
   <li> Immutable artifacts </li>
@@ -69,11 +69,11 @@
 enduring, and simple DVCS than one that looks pretty.</p>
 
 <p>On the other hand, if you have patches that improve the apparance
 of Fossil without seriously compromising its reliablity, performance,
 an maintainability, I will be happy to accept them.  Fossil is
-self-hosting.  Write to the maintainers for a password that will let
+self-hosting.  Send me email to request a password that will let
 you push to the main fossil repository.</p>
 </blockquote>
 
 <b>It would be useful to have a separate application that
 keeps the bug-tracking database in a versioned filed. That file can
@@ -86,11 +86,11 @@
 
 <b>Fossil is already the name of a plan9 versioned
 append-only filesystem.</b>
 
 <blockquote>
-I did not know that.  Perhaps they choose the name for the same reason that
+I did not know that.  Perhaps they selected the name for the same reason that
 I did: because a repository with immutable artifacts preserves
 and excellent fossil record of a long-running project.
 </blockquote>
 
 <b>The idea of storing a repository in a binary blob like an
@@ -112,18 +112,20 @@
 Subversion or Bazaar.</b>
 
 <blockquote>
 <p>I have no doubt that Trac has many features that fossil lacks.  But that
 is not the point.  Fossil has several key features that Trac lacks and that
-the primary fossil author cannot live without:  most notably the fact that
+I cannot live without:  most notably the fact that
 fossil supports disconnected operation.</p>
 
-<p>As for bloat:  Fossil is a single fully self-contained executable.
-You do not need any external packages in order to run fossil.  You do not
-need diff, patch, merge, cvs, svn, rcs, python, perl, tcl, sqlite, or anything
-else in order to run fossil.  Fossil runs just fine in a chroot jail all
-by itself.  And the self-contained executable is much less than 1MB in size.
+<p>As for bloat:  Fossil is a single self-contained executable.
+You do not need any other packages
+(diff, patch, merge, cvs, svn, rcs, git, python, perl, tcl, apache,
+sqlite, and so forth)
+in order to run fossil.  Fossil runs just fine in a chroot jail all
+by itself.  And the self-contained fossil
+executable is much less than 1MB in size.
 Fossil is the very opposite of bloat.</p>
 </blockquote>
 
 
 </nowiki>