linux-kernel - Re: [GIT PULL] non-MM commits for 6.2-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wjaO_S-kMb1n00suvnTBQS=mY2tH-YG9Tti_5pxnn_tzQ@mail.gmail.com>
Date:   Mon, 12 Dec 2022 18:44:18 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Vlastimil Babka <vbabka@...e.cz>,
        "Jason A. Donenfeld" <Jason@...c4.com>, linux-mm@...ck.org,
        mm-commits@...r.kernel.org, linux-kernel@...r.kernel.org,
        Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [GIT PULL] non-MM commits for 6.2-rc1

On Mon, Dec 12, 2022 at 6:35 PM Andrew Morton <akpm@...ux-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