The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Cgroups <cgroups@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] cgroup changes for v5.14-rc1
Date: Thu, 1 Jul 2021 14:32:02 -1000	[thread overview]
Message-ID: <YN5egtsVvp3xIqCl@mtj.duckdns.org> (raw)
In-Reply-To: <CAHk-=wgcyjLGcoRho5iw7b3Yx+R05rXwyJmP_LhOqsHgjiZugQ@mail.gmail.com>

Hello,

On Thu, Jul 01, 2021 at 05:25:59PM -0700, Linus Torvalds wrote:
> On Thu, Jul 1, 2021 at 1:55 PM Tejun Heo <tj@kernel.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).

for-5.13-fixes had comment updates across the file and I pulled them into
for-5.14 to avoid trivial context conflicts down the line. Yeah, I should
have commented on the rationale. Will add explanations from now on.

Thanks.

-- 
tejun

  reply	other threads:[~2021-07-02  0:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01 20:55 [GIT PULL] cgroup changes for v5.14-rc1 Tejun Heo
2021-07-02  0:25 ` Linus Torvalds
2021-07-02  0:32   ` Tejun Heo [this message]
2021-07-02  0:46 ` pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YN5egtsVvp3xIqCl@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox