On Tue, Jul 18, 2017 at 8:51 AM, Doug Ledford <dledford@xxxxxxxxxx> wrote:
>
> This is the first round of fixes for the -rc cycle.
Pulled. However, I want to complain (again!) about bad merge commits.
You're not the only one doing this, so this is not rdma-specific, but
I complain when I notice.
There's a merge commit in there that has no explanation. This is the
totality of the commit message:
Merge tag 'v4.13-rc1' into k.o/for-4.13-rc
Linux v4.13-rc1
and I want to point out that there is *nothing* there that explains
why that merge exists.
Dammit, if you cannot explain why a merge exists, you should not do
that merge! It's that simple.
There is absolutely no excuse for commits without explanations, and
that is *doubly* true of merge commits that don't even have any sane
patch associated with them.
A normal commit that does an obvious one-liner fix? It really may not
need more than a trivial commit message saying "Fix typo in xyz". The
rest of the commit explains it well enough.
A merge? There *has* to be an explanation for why the merge exists.
What problem did that merge fix? Why was it done in the first palce?
And if the only reason for that merge is "sync with upstream", then
no, that is not a sufficient reason. It has to have an actual real
reason, and it needs to be stated.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
