Message ID | 20211101152139.9019160F3A@mail.kernel.org (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [GIT,PULL] SPI updates for v5.16 | expand |
On Mon, Nov 1, 2021 at 8:21 AM Mark Brown <broonie@kernel.org> wrote: > > This is quite a quiet release for SPI, there's been a bit of cleanup to > the core from Uwe but nothing functionality wise. You continue to have these completely invalid merge commits that don't actually say what they merge and *WHY*: These four have one single line of "explanation": 531558b56be5 Merge branch 'spi-5.15' into spi-5.16 5fe7bd5a37ff Merge branch 'spi-5.15' into spi-5.16 66ae258ccf40 Merge branch 'spi-5.15' into spi-5.16 becbca18ae8f Merge existing fixes from spi/for-5.15 which is not good. And the ones that aren't one-liners have pointless other garbage in them in addition to the actual useful information. Things like Hello, ... Best regards Uwe ... base-commit: 9e1ff307c779ce1f0f810c7ecce3d95bbae40896 -- 2.30.2 are just complete noise that seems to indicate that you automate your merges with garbage, instead of actually editing them and making them be meaningful. STOP DOING THIS. Seriously. The commit messages for merges are important. They should explain what the merge dows and why it exists, but it also shouldn't contain random garbage from the email of the person who sent you a pull request. Linus
The pull request you sent on Mon, 01 Nov 2021 15:21:23 +0000:
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-v5.16
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2019295c9ea3137364682046bb6afc0eb364e591
Thank you!