This is not about "embarrassment", I was talking specifically about bisect. Bisect needs every commit to be usable; and this, in turns needs either mutable hist

This is not about "embarrassment", I was talking specifically about bisect. Bisect needs every commit to be usable; and this, in turns needs either mutable history, superhuman programmers, or manual file copy. So do many other things -- for example, cherry-picking is almost impossible if the feature is spread over tens of commits. I agree about not changing published history. But you don't need Fossil for that -- gitlab, github and even vanilla git all have ways to make master branch "fast-forward-only", which eliminates this problem. And if you are worried about "here-today, gone-tomorrow commits", git has a per-branch flag to prevent rebases and warn you loudly about them. I agree that working in the open is good, but again, there is no need for Fossil for that -- that's what "sandbox" branches are for. As long as you don't push incomplete work to master, you can share it easily.