<h1>The f-tools</h1>

The source tree contains a few test/demo apps which are named <tt>f-something</tt> (the "f" is for "fossil", of course). Collectively, these apps demonstrate the functionality which is currently ported in from fossil(1) (or is new) and working. If a fossil(1) feature is not represented here, it's probably not yet ported.

   *  <tt>[/finfo?name=f-acat.c|f-acat]</tt> ("artifact cat") can output arbitrary artifacts from a repository.
   *  <tt>[/finfo?name=f-config.c|f-config]</tt> lists the contents of the various configuration sources.
   *  <tt>[/finfo?name=f-config.c|f-config]</tt> lists and modifies the contents of the various configuration tables (global, repo, and local checkout).
   *  <tt>[/finfo?name=f-ls.c|f-ls]</tt> lists files from a repository.
   *  <tt>[/finfo?name=f-mfparse.c|f-mfparse]</tt> reads in Fossil control artifacts, converts them to its internal high-level form, and saves them back out to a file. This is used for testing both the manifest parsing and generation code, to test round-trip fidelity and compatibility with fossil(1) manifests.
   *  <tt>[/finfo?name=f-new.c|f-new]</tt> creates new/empty repository databases.
   *  <tt>[/finfo?name=f-query.c|f-query]</tt> runs SQL commands against a repo/checkout db. Be careful!
   *  <tt>[/finfo?name=f-resolve.c|f-resolve]</tt> resolves symbolic checkin names (like "trunk", "current", and "prev") and partial UUIDs to their full UUIDs and RIDs.
   *  <tt>[/finfo?name=f-sanity.c|f-sanity]</tt> runs a number of sanity checks on the library. Library developers should run/amend this occasionally.
   *  <tt>[/finfo?name=f-status.c|f-status]</tt> behaves mostly like fossil's <tt>status</tt> command.