Linus Torvalds writes: (Summary) It annoys me that our merge logs are sometimes really
bad.
bad.
I encourage maintainers to do
I encourage maintainers to do
git log --merges
git log --merges
and just look at the result.
and just look at the result.
I very much try to make *my* merges be informative, and - in order to get them to that point - I obviously require help from maintainers in the form of good pull requests. And for back merges, where you aren't merging some clear development history from a topic branch of your own or a submaintainer, the merge really *needs* an explanation. But you should have looked at the merge, and realized you didn't actually have any work, and told yourself "I shouldn't _merge_ v4.14, I should just update to it!"
_merge_ v4.14, I should just update to it!"
So one of the reasons I want to see explanations for merges is literally to avoid the _mindless_ merges.
bad.
I encourage maintainers to do
I encourage maintainers to do
git log --merges
git log --merges
and just look at the result.
and just look at the result.
I very much try to make *my* merges be informative, and - in order to get them to that point - I obviously require help from maintainers in the form of good pull requests. And for back merges, where you aren't merging some clear development history from a topic branch of your own or a submaintainer, the merge really *needs* an explanation. But you should have looked at the merge, and realized you didn't actually have any work, and told yourself "I shouldn't _merge_ v4.14, I should just update to it!"
_merge_ v4.14, I should just update to it!"
So one of the reasons I want to see explanations for merges is literally to avoid the _mindless_ merges.