* immutable
* built in first-class ticketing system
Happens to use SQLite as its storage engine too (SQLInception?), which brings at least a couple (off the top of my head) features:
* SQL is used to query things, which is very powerful
* the repository is a single SQLite file. Easy to store, copy, and…
* one can checkout multiple working copies into various directories. Or, in other words, I can have three discrete, independent workflows happening simultaneously, but only one copy of the repository backing them all.
It’s also got a built-in server that you can use locally or publish for remote people to access via their web browser that’s essentially GitHub-in-a-box.
Also… (kidding. I’m just going to stop here).
Edit: formatting
But fossil is a pleasure to work with, especially on Windows, because a) it comes as a single executable that one can just copy to another machine, and b) it does not require ssh or anything else to be installed.
The web interface is amazing, especially considering the size of the executable file.
The git workflow in the docs (https://git-scm.com/docs/git-worktree) looks really clunky.
Here’s what I do in fossil:
$ cd ~/work/project_x
$ fossil open ../fossils/projx.fsl (Edit, edit, edit)
$ fossil ci -m ‘descriptive msg’
(Get an idea, but for whatever reason do not want to disturb this directory)
$ mkdir ~/work/radical_idea
$ cd ~/work/radical_idea
$ fossil open ../fossils/projx.fsl <*note here there is no sense of this being an inferior or “sub” checkout*> (Edit, edit, edit)
$fossil ci -m “cool idea” —branch cool_idea # commit work to new branch
(Test..)
$ fossil co trunk #switch branch back to trunk
$ fossil merge cool_idea #merges our work from cool_idea branch into trunk branch
$ fossil ci -m ‘merge [cool_idea] for radical new feature’
$ fossil close # this working dir syncs everything necessary to the repo (../fossils/projx.fsl) and is now essentially “offline”
$ cd ..; rm -fr radical_idea
$ cd project_x (Note: this working directory now not a tip of trunk anymore…)
$ fossil update # now up to speed (Continue hacking…)
In Git, that'd be:
$ cd ~/work/fossils/projx.git
$ git worktree add ~/work/project_x master # add a worktree with the 'master' branch checked out
$ cd ~/work/project_x
(Edit, edit, edit) $ git commit -m 'descriptive msg'
(Get an idea, but for whatever reason do not want to disturb this directory) $ git worktree add ~/work/radical_idea -b cool_idea # add a worktree with a new 'cool_idea' branch
$ cd ~/work/radical_idea
(Edit, edit, edit) $ git commit -m "cool idea"
(Test..) $ git switch master # whoops, can't do this
fatal: 'master' is already checked out at '~/work/project_x'
$ # let's just do the merge in the other worktree, since we're about to switch anyway
$ cd ~/work/project_x
$ git worktree remove ~/work/radical_idea # or: rm -rf ~/work/radical_idea && git worktree prune
$ git merge cool_idea
(Continue hacking…)There is not in worktrees either. You can use worktrees with a bare repository for instance. It's just that for backwards compatibility and the convenience of most users a non-bare clone creates a default worktree. That's exactly what you see if you `git clone` a repository then `git worktree list`, a worktree corresponding to the working copy.
Also quite interesting the general comparison: https://fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki
Both sites are written from Fossil guys, so they may not be 100% neutral.
I'm going to have to dig to see if he describes somewhere why Fossil is such a great fit for SQLite.