> In my books its a minus that you can not rewrite history. To quote Richard Hipp, the primary author of Fossil and SQLite [1]: "Fossil, in contrast, is desig

> In my books its a minus that you can not rewrite history. To quote Richard Hipp, the primary author of Fossil and SQLite [1]: "Fossil, in contrast, is designed to remember everything. Fossil was specifically designed to support the DO-178B inspired development process used by SQLite, with few developers and a complete and immutable audit trail for all inputs." About DO-178B: https://en.wikipedia.org/wiki/DO-178B https://en.wikipedia.org/wiki/DO-178B In short: Fossil is designed for a different purpose than Git. Note that even then, in Fossil – as with every system that represents data in purely electronic format – nothing is truly immutable. And Fossil does have ways to excise data from history (shunning, "fossil purge", etc.). You can even run raw SQL queries on the underlying SQLite database if you want or use "fossil deconstruct/reconstruct" to break down a repository into its constituent artifacts and rebuild it. However, these are generally methods of last resort and there are no frontend facilities to easily integrate them into your workflow (other than, arguably, "fossil purge", which is local only). [1] https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg19555.html https://www.mail-archive.com/fossil-users@lists.fossil-scm.o...