From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: meta@public-inbox.org
Subject: RFC: hooks in public-inbox-watch
Date: Thu, 12 May 2022 14:04:42 -0400 [thread overview]
Message-ID: <20220512180442.ais2ujjolq53vkio@meerkat.local> (raw)
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
next reply other threads:[~2022-05-12 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 18:04 Konstantin Ryabitsev [this message]
2022-05-12 19:38 ` RFC: hooks in public-inbox-watch Eric Wong
2022-05-12 19:54 ` Konstantin Ryabitsev
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220512180442.ais2ujjolq53vkio@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).