linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 mm-commits@vger.kernel.org
Subject: Re: [GIT PULL] hotfixes for 6.1-rc2
Date: Fri, 21 Oct 2022 12:40:12 -0700	[thread overview]
Message-ID: <CAHk-=wgb42XG1c_rtwupJMD9QXbJsE6k_TBKYC4YvZ8bkATcVg@mail.gmail.com> (raw)
In-Reply-To: <20221020213327.2c284af5925b6a8ed915fe9e@linux-foundation.org>

On Thu, Oct 20, 2022 at 9:33 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> Andrew Morton (3):
>       Merge branch 'master' into mm-hotfixes-stable
>       Merge branch 'master' into mm-hotfixes-stable

I've pulled this, but both of these merges look entirely invalid.

First off, one of them is most definitely pointless - there's no
activity between the first and the second merge, so that first merge
shouldn't have been done in the first place.

But the second merge is bad by definition too, in that it doesn't have
any explanation for it.

I've said this before - and I hope that some day I just won't have to
say it again - if you cannot explain a merge, you shouldn't be *doing*
a merge.

It really is that simple. If you have no clear explanation for why you
need to do that merge, then you simply shouldn't have done it.

For example, that first merge clearly CANNOT have a valid reason for
existing. There's simply no valid explanation for doing it,
considering that there was no work on top of it that could possibly be
a cause tor that merge.

So that whole "if you cannot explain why you do a merge, don't do the
merge" rule should have been a hard "NO" on it, and should have made
it obvious that it shouldn't have happened.

Please don't do pointless merges.

            Linus


  reply	other threads:[~2022-10-21 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  4:33 Andrew Morton
2022-10-21 19:40 ` Linus Torvalds [this message]
2022-10-21 19:43 ` 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='CAHk-=wgb42XG1c_rtwupJMD9QXbJsE6k_TBKYC4YvZ8bkATcVg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.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