Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: stable@vger.kernel.org,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>,
	linux-kernel@vger.kernel.org,  tools@linux.kernel.org,
	Willy Tarreau <w@1wt.eu>
Subject: Re: [ANNOUNCE] New script that finds partially-backported patchsets
Date: Mon, 1 May 2023 11:36:41 -0400	[thread overview]
Message-ID: <20230501-deskwork-imprison-fc8451@meerkat> (raw)
In-Reply-To: <20230430064948.GA36600@sol.localdomain>

On Sat, Apr 29, 2023 at 11:49:48PM -0700, Eric Biggers wrote:
> - `find-orig-patch`: Finds the original patch email from a git commit.
>    It first checks for a matching "Message-Id:" or "Link:" from the git commit.
>    If that fails, it falls back to a search of https://lore.kernel.org by
>    commit title and uses some heuristics to try to find the right patch email.

You should also try matching by patch-id. E.g., taking the commit from the
example:

    $ git show de534c1cb031 | git patch-id --stable
    7d23fb78b4bb892155827a612631168cb28584cc de534c1cb0313a070f45938a53b53927cd34e5b9

Then we can search by patchid:7d23fb78b4bb892155827a612631168cb28584cc:

    https://lore.kernel.org/all/?q=patchid%3A7d23fb78b4bb892155827a612631168cb28584cc

-K

      parent reply	other threads:[~2023-05-01 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-30  6:49 [ANNOUNCE] New script that finds partially-backported patchsets Eric Biggers
2023-04-30 15:29 ` Sasha Levin
2023-05-01 15:36 ` Konstantin Ryabitsev [this message]

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=20230501-deskwork-imprison-fc8451@meerkat \
    --to=konstantin@linuxfoundation.org \
    --cc=ebiggers@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tools@linux.kernel.org \
    --cc=w@1wt.eu \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).