fossil - Distributed Version Control System
fossil help COMMAND
fossil COMMAND [OPTIONS]
Fossil is a distributed version control system (DVCS) with built-in wiki, ticket
tracker, CGI/http interface, and http server.
add changes gdiff publish status
addremove clean help pull sync
all clone import push tag
amend commit info rebuild timeline
annotate delete init remote-url ui
bisect diff ls revert undo
blame export merge rm unpublished
branch extras mv settings unversioned
bundle finfo open sqlite3 update
cat fusefs praise stash version
Features as described on the fossil home page.
Integrated Bug Tracking, Wiki, & Technotes
- In addition to doing
distributed version control like Git and Mercurial, Fossil also supports bug
tracking, wiki, and technotes.
Built-in Web Interface
- Fossil has a built-in and intuitive web
interface that promotes project situational awareness. Type "fossil
ui" and Fossil automatically opens a web browser to a page that shows
detailed graphical history and status information on that project.
- Fossil is a single self-contained stand-alone
executable. To install, simply download a precompiled binary for Linux, Mac,
OpenBSD, or Windows and put it on your $PATH. Easy-to-compile source code is
available for users on other platforms.
- No custom protocols or TCP ports. Fossil uses plain old HTTP
(or HTTPS or SSH) for all network communications, so it works fine from behind
restrictive firewalls, including proxies. The protocol is bandwidth efficient
to the point that Fossil can be used comfortably over dial-up.
- No server is required, but if you want to set one
up, Fossil supports four simple server configurations.
- Fossil supports "autosync" mode which helps to
keep projects moving forward by reducing the amount of needless forking and
merging often associated with distributed projects.
- Fossil stores content using an enduring file format in an
SQLite database so that transactions are atomic even if interrupted by a power
loss or system crash. Automatic self-checks verify that all aspects of the
repository are consistent prior to each commit. In over seven years of
operation, no work has ever been lost after having been committed to a Fossil