Re: Fetch-hooks

From: Leo Gaspard <leo@gaspard.io>
Date: Feb 13, 2018, 15:44 UTC
Message-ID: <461e515c-350a-50f2-bc13-6a976df489fd@gaspard.io>
In-Reply-To: <20180212192327.GA209601@google.com>

On 02/12/2018 08:23 PM, Brandon Williams wrote:> Maybe this isn't helpful but you may be able to implement this by using

> a remote-helper.  The helper could perform any sort of caching it needed
> to prevent re-downloading large amounts of data that is potentially
> thrown away, while only sending through the relevant commits which
> satisfy some criteria (signed, etc.).

This looks like a possibility, thanks! I'll likely try to implement it this way if there can be no consensus on the features wanted for a fetch-hook (as the current state of discussion looks like to me).

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.