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.4 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, 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-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (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 41C421F4D7 for ; Thu, 12 May 2022 18:04:46 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="DZm+bh//"; dkim-atps=neutral Received: by mail-qk1-x736.google.com with SMTP id z126so5389824qkb.2 for ; Thu, 12 May 2022 11:04:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mime-version:content-disposition; bh=1an3pDxF3z+fF1n51VaPkmDYlBipKQ3ykQVyXTJvwVo=; b=DZm+bh//ocbfBCOlMMiA966RXOjiPdQVwfrKobGG+BRrVZdjr7lNikQmEpukJI9Ozg gWF5CqCcD6nY6mJ12eMxAKW7d0zveHhkbuzP1wMrzPTS4TLZNvGoXqCSe8ekNO1v1McY E7MF2HarMTre6KmBVEMKS0k9duozXypi3LQqY= 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:subject:message-id:mime-version :content-disposition; bh=1an3pDxF3z+fF1n51VaPkmDYlBipKQ3ykQVyXTJvwVo=; b=oTSOKwXUDTnzdnyAabz29dpKUmtZphMIpHraWFtNHgjF3HMX0N86KriIkx9lB3MkaL RlDBwkXl5njl0O7dGlpZ3ntCKUhJQsBbg0WT1jcUc4x1uWmXSxSxLMPq7IGYDazdCuxp NJow2/zHm+DwX+TLZOCiHJoBeEwW59LAX9H2vn9DqByB0xb7R2FDwdRAimapKtl+ol/X 7x9GjcWEyg8Url8OQ6uAgHiuhE3V22JpdT7otSShcOKPujwCrI3p0RYy4bamwdXatCRU Ga5fk1CNfl07OqRf7jPRVZ7zdim/M2/ernw4So+lJ0bdf+5BZ1jA06DQXDX0s51MuQ58 20HA== X-Gm-Message-State: AOAM5306Z6ISHm8GXEFB0NWlbpUByW0M2nqBPXGytXeEfSIDMMORxJzH 20Xu6X/g3u0zaOX2SiJNmTKE8G3PrVkqSg== X-Google-Smtp-Source: ABdhPJz6o7FtSXhyDX4tqshq1gvdw94/IN+ok0Bwb8y6lMlwBMFtFN56kGFloRvoOZ1bjMKs8OG/8g== X-Received: by 2002:a37:2786:0:b0:6a0:f9db:1a7b with SMTP id n128-20020a372786000000b006a0f9db1a7bmr901804qkn.440.1652378684775; Thu, 12 May 2022 11:04:44 -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 c85-20020a379a58000000b0069fc167df92sm66813qke.82.2022.05.12.11.04.44 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 12 May 2022 11:04:44 -0700 (PDT) Date: Thu, 12 May 2022 14:04:42 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: RFC: hooks in public-inbox-watch Message-ID: <20220512180442.ais2ujjolq53vkio@meerkat.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: 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 I know this can be done at the postfix stage, but seems like it would be more efficient at the ingestion stage. Maybe even instead of a hook this could be a native public-inbox feature, with this header being indexed by default? -K