Check-in [3c1234c0f2]
Not logged in
Overview

SHA1 Hash:3c1234c0f25af3aa3447a0f728c82d90f44229b1
Date: 2009-09-12 17:45:00
User: drh
Comment:More documentation updates.
Timelines: ancestors | descendants | both | trunk
Other Links: files | ZIP archive | manifest

Tags And Properties
Changes
[hide diffs]

Modified www/concepts.wiki from [bf268d18d1] to [44bd9b89f6].

@@ -148,11 +148,12 @@
 and links to other check-ins from which the current check-in
 is derived.  There is also a couple of checksums used to verify
 the integrity of the check-in.  And the whole manifest might
 be PGP clearsigned.</p>
 
-<h3><a name="keyconc">2.3</a> Key concepts</h3>
+<a name="keyconc"></a>
+<h3>2.3 Key concepts</h3>
 
 <ul>
 <li>A <b>check-in</b> is a set of files arranged
     in a hierarchy.</li>
 <li>A <b>repository</b> keeps a record of historical check-ins.</li>
@@ -167,13 +168,16 @@
 </ul>
 
 <h2>3.0 Fossil - The Program</h2>
 
 Fossil is software.  The implementation of fossil is in the form
-of a single executable named "fossil".  To install fossil on your system,
+of a single executable named "fossil" (or "fossil.exe" on windows).
+To install fossil on your system,
 all you have to do is obtain a copy of this one executable file (either
-by downloading a pre-compiled version or compiling it yourself) and then
+by downloading a
+<a href="http://www.fossil-scm.org/download.html">pre-compiled version</a>
+or [./build.wiki | compiling it yourself]) and then
 putting that file somewhere on your PATH.
 
 Fossil is completely self-contained.  It is not necessary to
 install any other software in order to use fossil.  You do <u>not</u> need
 CVS, gzip, diff, rsync, Python, Perl, Tcl, Java, apache, PostgreSQL, MySQL,
@@ -205,11 +209,11 @@
 
 In the next section, when we say things like "use the <b>help</b>
 command" we mean to use the command name "help" as the first
 token after the name of the fossil executable, as shown above.
 
-<a name="workflow">
+<a name="workflow"></a>
 <h2>4.0 Workflow</h2>
 
 <img src="concept2.gif" align="right" hspace="10">
 
 Fossil has two modes of operation: <i>"autosync"</i> and
@@ -379,11 +383,11 @@
 a lot of work and normally takes time, patience, and a lot of system
 knowledge.  Fossil is designed to avoid this frustration.  Setting up
 a server with fossil is ridiculously easy.  You have three options:</p>
 
 <ol>
-<li><b><a name="saserv">S</a>etting up a stand-alone server</b>
+<li><b><a name="saserv"></a>Setting up a stand-alone server</b>
 
 From within your source tree just use the <b>server</b> command and
 fossil will start listening for incoming requests on TCP port 8080.
 You can point your web browser at <a href="http://localhost:8080/">
 http://localhost:8080/</a> and begin exploring.  Or your coworkers

Modified www/quickstart.wiki from [c14ac831a6] to [641af43c5f].

@@ -12,11 +12,13 @@
     <a href="http://www.fossil-scm.org/download.html">precompiled binary</a>
     or <a href="build.wiki">build it yourself</a> from sources.
     Install fossil by putting the fossil binary
     someplace on your PATH environment variable.</p>
 
-</blockquote><h2>Cloning An Existing Repository</h2><blockquote>
+</blockquote>
+<a name="fslclone"></a>
+<h2>Cloning An Existing Repository</h2><blockquote>
 
     <p>Most fossil operations interact with a repository that is on the
     local disk drive, not on a remote system.  Hence, before accessing
     a remote repository it is necessary to make a local copy of that
     repository.  Making a local copy of a remote repository is called
@@ -105,11 +107,11 @@
     <b>fossil status</b><br>
     <b>fossil changes</b><br>
     <b>fossil timeline</b><br>
     <b>fossil leaves</b><br>
     <b>fossil ls</b><br>
-    <b>fossil branch list</b><br>
+    <b>fossil branches</b><br>
     </blockquote>
 
 </blockquote><h2>Making Changes</h2><blockquote>
 
     <p>To add new files to your project, or remove old files, use these