From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: cgit@lists.zx2c4.com
Subject: Re: RFE: commit git-patch-id lookup links
Date: Fri, 7 Oct 2022 21:14:49 +0000 [thread overview]
Message-ID: <20221007211449.M581921@dcvr> (raw)
In-Reply-To: <20221007172528.4ryaoc26wwtsetdw@meerkat.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Hi, all:
>
> One of the recent additions to public-inbox was auto-indexing of patches by
> their patch-id (see git-patch-id.1). This allows to see a history of many
> commits through public-inbox discussions. Using a random commit as an example:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e4dc45b1848bc6bcac31eb1b4ccdd7f6718b3c86
>
> We can convert it to a patch-id and look up its history:
>
> $ echo "https://lore.kernel.org/all/?q=patchid:$(git show e4dc45b1848 | git patch-id --stable | awk '{print $1}')"
> https://lore.kernel.org/all/?q=patchid:d91c951338cfe9f06e8b8aa74856f6dc08ac8212
Fwiw, patchid: doesn't account for some cases where non-standard options
are used for generating patches (e.g. -W, -U<n>). Admittedly they're
rare cases...
I've been favoring searches for postimage blob IDs (since pre-patchid
in public-inbox), possibly combined with Subject: phrase matches.
Fwiw, public-inbox can show git commits and prefill search forms:
https://public-inbox.org/git/d1e76d5ddcacdfc76bc247e7594e3fbaaa5ea9cc/s/
the top search form has `patchid:' pre-filled, and the form below the
patch has `dfblob:' pre-filled. Subject (`s:') isn't pre-filled, yet
(haven't decided how to signify that's optional in the UI).
prev parent reply other threads:[~2022-10-07 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 17:25 Konstantin Ryabitsev
2022-10-07 21:14 ` Eric Wong [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=20221007211449.M581921@dcvr \
--to=e@80x24.org \
--cc=cgit@lists.zx2c4.com \
--cc=konstantin@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).