> If you like a readable commit history, rebase is useful to reorder and squash unnecessary commits. This is an artifact of Git. There are two principal soluti

> If you like a readable commit history, rebase is useful to reorder and squash unnecessary commits. This is an artifact of Git. There are two principal solutions that do not require rebase. 1. Use Bzr-style hierarchical logs. This could in principle be used as a UI on top of Git. Here, merging rather than rebasing actually improves the readability of history. 2. Have fully labeled branches. This allows you to filter and visualize commit history based on branch membership. This is the approach traditionally used by most non-Git version control systems, but is not really viable in Git, because Git lacks the necessary meta information.