1. Fossil is designed around having auditable history. 2. Fossil can change meta-information (commit messages, tags, branch names) after the fact. Those change

1. Fossil is designed around having auditable history. 2. Fossil can change meta-information (commit messages, tags, branch names) after the fact. Those changes also leave an audit trail. 3. Fossil has features that handle certain use cases for rebasing (private branches, fossil stash snapshot, etc.). If you absolutely need to, fossil purge can be used to edit local history and the shun mechanism can be used to (e.g.) extirpate sensitive information that was shared by accident. 4. Extensive use of rebasing to produce a linear history is a Git-ism , largely due the fact that in Git, history is a soup of anonymous commit objects that is difficult to visualize. Other version control systems that allow you to label and structure history have less need for this.