Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20221212134425.b20b80955e5e8a4a36ce1b9a@linux-foundation.org>
 <Y5eoS/UfBhovR70j@zx2c4.com> <20221212142754.5f699c4ff515fd9d42768fb2@linux-foundation.org>
 <e7c6b99a-743f-f40a-0b0f-31730964cb36@suse.cz> <20221212183554.e0a2536e860172282b189ca4@linux-foundation.org>
In-Reply-To: <20221212183554.e0a2536e860172282b189ca4@linux-foundation.org>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon, 12 Dec 2022 18:44:18 -0800
Message-ID: <CAHk-=wjaO_S-kMb1n00suvnTBQS=mY2tH-YG9Tti_5pxnn_tzQ@mail.gmail.com>
Subject: Re: [GIT PULL] non-MM commits for 6.2-rc1
To:     Andrew Morton <akpm@linux-foundation.org>
Cc:     Vlastimil Babka <vbabka@suse.cz>,
        "Jason A. Donenfeld" <Jason@zx2c4.com>, linux-mm@kvack.org,
        mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
        Stephen Rothwell <sfr@canb.auug.org.au>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, Dec 12, 2022 at 6:35 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> Well here's a hacky thing - just look for duplicated patch titles after
> stripping away the hashes.

Please don't do that.

Just use the git machinery that Vlastimil pointed at.

"git cherry" uses the actual patch ID (which is just a hash of the
patch with whitespace removed), so it actually looks at the patch
itself, not just eh first line of the commit message.

If you insist on writing your own shell script for this, please use
that same "patch-id" logic. That's made available by "git patch-id".

But do "man git-cherry" and "man git-patch-id" before you do any of that.

And in no situation should you go "the first line of the commit
message is identical, so the patches must be the same".

                     Linus