← Back to context

Comment by zaphar

1 day ago

Maybe it's time for fossil to get another look... It's effectively distributed code, wiki, and issues all using the same tool.

Every time Fossil comes up, people's big objection is that you can't squash commits. Personally, I'm fine with that - I tend to agree with Hipp that the repo history should not sacrifice truth for the sake of pettiness in the timeline. But a lot of people seem to disagree, which limits the audience for Fossil. I use Fossil for my own projects but I wouldn't expect it to become big like git is.

  • Mailing patches is the same as squashing commits. The Linux kernel would be much harder to maintain without messy history being carefully distilled down to well crafted patches.

    But mailing patches is a pain in the ass. VCSes should support squashing and rebasing.