directory, or else that the --force flag be used which overwrites all local
changes.</i>

If there is a well-defined difference between update and checkout, I am fine with them being separate.  Prior to your explanation, they seemed so similar it was arbitrary that they be kept separate.  Checkout selects exactly a particular checkout.

------
*On 2016-05-15 07:05:24 UTC sdr added:*

# Interfaces to extend fossil

SQLite enjoys great extensibility through user defined functions and virtual tables (and of course VFS). There are people who would like this- or that-functionality implemented into fossil directly but there is resistance to the specific bit of functionality.

What about a way to register extensions with fossil? Such as a mailing list or forum or I have no idea what else?

Today, one is free to fork the project and maintain their fork. In the future it could be possible for people to maintain their functionality independently of fossil and just add it as part of the build process.