??? You could just make a temp2 branch, from master at the same branching point as temp1, and then periodically create your astonishingly beautiful commits fro

??? You could just make a temp2 branch, from master at the same branching point as temp1, and then periodically create your astonishingly beautiful commits from the horridly messy temp1, to temp2. And then merge temp2 to master, when you want. The only "sin" fossil commits here is that temp1 is still there, if you want to see what you ACTUALLY did (yes, I fully accept that your beautifully crafted commits are totally bug-free). And here's the real kicker: the fossil ui is easily customizable so that certain branches (eg: "tmp-...") can be hidden from the timeline view, so they don't get in the way. I believe the sqlite team (inc DRH) have hundreds of "tmp" branches, whose only purpose is "messy commits, clean up later" (yup, you can refuse the same branch name as many times as you like, easier for auto-hiding.