3 ms·
It is useful for when you want the commits to be clearly grouped in the log (because they belong together conceptually), but you don't want to squash them all t
by rchipman 10y ago
It is useful for when you want the commits to be clearly grouped in the log (because they belong together conceptually), but you don't want to squash them all together (because, for example, you still want to be able to browse/bisect/revert some of those commits in the future). Also, it is easy to revert the merge commit if you want to undo the whole group at once.
- lmm 10y ago> It is useful for when you want the commits to be clearly grouped in the log (because they belong together conceptually) Surely there must be a way to tell git to show history in that form even with branches that haven't been rebased?