From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 13939 invoked from network); 7 Oct 2022 21:15:10 -0000 Received: from lists.zx2c4.com (165.227.139.114) by inbox.vuxu.org with ESMTPUTF8; 7 Oct 2022 21:15:10 -0000 Received: by lists.zx2c4.com (OpenSMTPD) with ESMTP id e8becd3d; Fri, 7 Oct 2022 21:14:53 +0000 (UTC) Return-Path: Received: from dcvr.yhbt.net (dcvr.yhbt.net [173.255.242.215]) by lists.zx2c4.com (OpenSMTPD) with ESMTPS id 918fa9d1 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO) for ; Fri, 7 Oct 2022 21:14:51 +0000 (UTC) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id BA7891F403; Fri, 7 Oct 2022 21:14:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=80x24.org; s=selector1; t=1665177289; bh=GjilvQg0sc5xuFd3XHEUHB8nKnmB7gEgQmoaHfPsB6o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=qwvzVJfvIpZ72JImXT/JJu7Jo2K1fMb8oQUfYeB+XzJEf7U3n2lEcuMGhuaNBaphs ffFuW+cySlpXM/EUxTamSjgkMMAUvagmyT5q/37rEYC4kkx1XFK5ct6UQntYmxkOPV dgzgCb2uknBb1wEoBQmHEhClOaGVQKawFdpmYXwI= Date: Fri, 7 Oct 2022 21:14:49 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: cgit@lists.zx2c4.com Subject: Re: RFE: commit git-patch-id lookup links Message-ID: <20221007211449.M581921@dcvr> References: <20221007172528.4ryaoc26wwtsetdw@meerkat.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20221007172528.4ryaoc26wwtsetdw@meerkat.local> X-BeenThere: cgit@lists.zx2c4.com X-Mailman-Version: 2.1.30rc1 Precedence: list List-Id: List for cgit developers and users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: cgit-bounces@lists.zx2c4.com Sender: "CGit" 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: > > 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). 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).