List for cgit developers and users
 help / color / mirror / Atom feed
From: Eric Wong <>
To: Konstantin Ryabitsev <>
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 <> 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:
> We can convert it to a patch-id and look up its history:
> $ echo "$(git show e4dc45b1848 | git patch-id --stable | awk '{print $1}')"

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:

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).

      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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221007211449.M581921@dcvr \ \ \ \

* 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).