On Tue, Sep 7, 2021 at 9:36 PM Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > Merge commits need explanations. They need explanations for why the > merge is done, and what the merge pulls in. Not this "single line that > doesn't explain anything". Good point, I think I am one of the offenders here as well, and I see there has been quite a bit of media stir about github doing blank merges like this by default (IIUC). I'll try to do it better going forward, it'd be nice if there is or could be a way to just configure a git tree to disallow blank commit messages, then we can configure the maintainer trees so that we just can't do it wrong, and if we mention this in Documentation/maintainer/configure-git.rst I think it would considerably improve things, I wonder if this is possible? Yours, Linus Walleij