[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgcyjLGcoRho5iw7b3Yx+R05rXwyJmP_LhOqsHgjiZugQ@mail.gmail.com>
Date: Thu, 1 Jul 2021 17:25:59 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Tejun Heo <tj@...nel.org>
Cc: Cgroups <cgroups@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] cgroup changes for v5.14-rc1
On Thu, Jul 1, 2021 at 1:55 PM Tejun Heo <tj@...nel.org> wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.14
I've pulled it, but let me vent about this history a bit.
Look at commit c2a11971549b ("Merge branch 'for-5.13-fixes' into for-5.14").
Now tell me how that commit explains why it exists.
Merge commits need commit messages too.
In particular, they need commit messages that *explain* why they exist
in the first place, not just a one-liner that says what it does (and
does so badly at that).
Linus
Powered by blists - more mailing lists