> We'll start with Fossil not tolerating `git rebase` or `git commit --amend`: https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.w https://www.fossil-s

> We'll start with Fossil not tolerating `git rebase` or `git commit --amend`: https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.w https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.w... and the number of repos I've seen where PRs don't land without someone chirping about "please rebase your branch" How's that "feature" of fossil ? You can just decide to not allow it in Git as you see fit, and it is something that is useful once you know how to. This whole set basically sounds like "Git allows you to do all that but fossil forces you to work its way". Which is fine but you could... just decide to do it in git. It does show that fossil is trying different approach, it doesn't want to be really distribute as much as just "synced"