<h1>How to use this repo</h1>

You can “use” this repo by clicking around and reading code, wiki pages,&nbsp;etc.

But you can also use it to work with your own copy of the code. I suspect this won’t be interesting or useful for 99% of the people reading this. But in the event that you’ve become a patron and want to try using Fossil to work with the code, here’s a quick guide on how to get started.

<ol>
<li>If you don’t already have it <a the Fossil executable and put it on
<li>Clone this repository:
<pre><code><b>&gt;</b> fossil clone
<li>You might as well set autosync to <tt>0</tt> (off) or to <tt>pullonly</tt>. (See below for more info about&nbsp;why):
<pre><code><b>&gt;</b> fossil settings autosync
<li>“Check out” the latest version of the source code into your current&nbsp;directory:
<pre><code><b>&gt;</b> fossil open
<li>Fiddle with the source code as you see fit. Read Quick Start].</li>
<li>You can also open your own local copy of the web&nbsp;UI:
<pre><code><b>&gt;</b> fossil
<li>To get the latest version of the&nbsp;code:
<pre><code><b>&gt;</b> fossil
</ol>

<h2>Some tips for Git users</h2>

  *  If you’re wondering why I’m using Fossil instead of Git, read [Why Fossil?]
  *  Fossil has <code>autosync</code> on by default, which means it will sync with the remote repo on every commit. But since you likely won’t have “push” privileges on my repo, it will fail. Turning autosync off will prevent you from having to see it try and fail every time you make a commit.
  *  There is no “staging” step in Fossil. Doing <a immediately commits all changes in all tracked files into the repository. If you need to, you can specify which file or files you want to be included in the&nbsp;commit.
  *  There is no selective “patch committing” in Fossil (i.e., <code>git add -p</code> in Git), reportedly because it facilitates check-ins of untested code. So, if you’re in the habit of making unrelated edits to it!]
  *  There is currently no “pull request” functionality in Fossil; users either have commit privileges or they don’t. This is fine for me since I am not interested in pull requests. If you would like to propose a change you can email me a patch.