From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.5 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 066CF1F4D7 for ; Thu, 12 May 2022 19:54:11 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="DbAdfo5q"; dkim-atps=neutral Received: by mail-qk1-x72e.google.com with SMTP id a76so5584457qkg.12 for ; Thu, 12 May 2022 12:54:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=9AzMI0Elxt9wsffbMgY4Vqu6Ks5RyHWZ953fjNIxveA=; b=DbAdfo5qUqHQeYlB0djtsf7fMtL8Jq4i0Lp8RKn3WmpvKcTKFTKsvOuK6rvgAnjnyp MDbD1EJ2V4rmSlJ4m42Gl+9Qow34f0+6w9H/0xIw6OuvJrBPrSgBjygtBJ+04C4tFaw5 R5r+PFciVVloow1TfNjn5sku3tWPLm3xz8o5A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=9AzMI0Elxt9wsffbMgY4Vqu6Ks5RyHWZ953fjNIxveA=; b=U0fKMeymifhN33qZKKtmWwz94l57ID/iZ7RoMVkiyx8jChngIWs1JHLLZKzYEigScs iwx681vapfRfohj6XRMV46m6hvv/OHtf8JqgnihPHAUUg+jJdjHszEG4Om1QFxr3QoLa YXYSeceRNm34s8TIHtJOIGhBQKtyCQG1JOGa6z/e/SJ8w8NOoK7n1BZ/b+Whr17d8Qpy eeXNsxU8pDnlAuxo4r+zOBZTBpaNDwvIHk/joWr8oBSNTXgIPc17zX9Ci08PKlbuw8vO np6FndZdjaBSxq2h6pbZ0JVKGW0HaTbQH09ohb/JonSKYXqFYeFYKX+x/fd91dsc1c4R etBA== X-Gm-Message-State: AOAM532KhLZLqydLEvzcLOF7xhfFUGXgQ6ohWtKMbGmUtH80EHspnczD epbHxE+/vvNF8W+BxJIEw60XVOic8J7+2g== X-Google-Smtp-Source: ABdhPJyXWIcAG7T6WzkmT64Z94Cfdk1ESjEgGnfOcDm0Bih7U1hN8MCj5Y4zT1Q7RPhKMQozZBYvMg== X-Received: by 2002:a05:620a:795:b0:69f:d074:6067 with SMTP id 21-20020a05620a079500b0069fd0746067mr1209494qka.527.1652385250030; Thu, 12 May 2022 12:54:10 -0700 (PDT) Received: from meerkat.local (bras-base-mtrlpq5031w-grc-32-216-209-220-127.dsl.bell.ca. [216.209.220.127]) by smtp.gmail.com with ESMTPSA id c24-20020ac84e18000000b002f39b99f69bsm264242qtw.53.2022.05.12.12.54.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 12 May 2022 12:54:09 -0700 (PDT) Date: Thu, 12 May 2022 15:54:07 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: RFC: hooks in public-inbox-watch Message-ID: <20220512195407.6w3citoz5jukoakj@meerkat.local> References: <20220512180442.ais2ujjolq53vkio@meerkat.local> <20220512193859.M526956@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20220512193859.M526956@dcvr> List-Id: On Thu, May 12, 2022 at 07:38:59PM +0000, Eric Wong wrote: > Konstantin Ryabitsev wrote: > > Hi, all: > > > > What do you think about a mechanism to run hooks at the stage right before > > public-inbox-watch adds a new message to the archive? One feature that would > > be neat is to search archives for all instances of the same patch using its > > $(git-patch-id --stable) and adding a header, e.g.: > > > > X-Git-Patch-ID: 19c05284cea20b72b44c2b7e6cfd782a6a860cf1 0000000000000000000000000000000000000000 > > There shouldn't be any need for a header. I've been meaning to > teach -index to use git-patch-id and index it's output, anyways. > That would work for old messages, too. Sure, I'll take that, too. :) Thanks, -K