4 ms·
That would be more useful, as git log tools tend not to deal fantastically well with concurrently running branch, especially with interleaved side-branches (for
by masklinn 10y ago
That would be more useful, as git log tools tend not to deal fantastically well with concurrently running branch, especially with interleaved side-branches (fork branch 1, fork branch 2, merge branch 1, merge branch 2, history looks like garbage in most Git tools)
- geofft 10y agoYou can get a lot better results with `git log -m --first-parent`, which effectively shows you only the merge commits, and shows all changes that were merged in as if they belonged to the merge commit. I have a `git log0` alias for this, as well as `git blame0` and `git show0`.
- masklinn 10y ago> You can get a lot better results with `git log -m --first-parent` Yes, however that only works in the CLI, not in any Git GUI I know of (though GTK Bazaar log would pretty much do that, folding merge commits & following the mainline by default).