Re: [RFC] origin link for cherry-pick and revert

From: Paolo Bonzini <bonzini@gnu.org>
Date: Sep 12, 2008, 15:40 UTC
Message-ID: <48CA8D6A.4000303@gnu.org>
In-Reply-To: <200809121711.32448.jnareb@gmail.com>

Show 8 quoted lines

>> I know you seem to be resistent to caches, but caches are **good**
>> because they are local information, which by definition can be
>> implementation-dependent; you can always generate the cache from the
>> git repository if for some reason you need to extend it. [...]
> 
> But it is not true that "you can always generate the cache from the
> git repository" in this case; the patch-id that is to be saved is
> _original_ patch-id of cherry-picked (or reverted) changeset.

He's proposing storing the original patch id in the commit message, and caching the commit SHA->patch id association on the side.

Paolo

$ 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.