git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH / RFC] cherry: cache commit to patch-id pairs to avoid repeating work

From
Geoffrey Irving <irving@naml.us>
Date
Jun 8, 2008, 05:39 UTC
Message-ID
<7f9d599f0806072239je3a7ec0q258d7770c15fa962@mail.gmail.com>
In-Reply-To
<7f9d599f0806071636j1df57b6eqb5808f083dafd6a2@mail.gmail.com>
On Sat, Jun 7, 2008 at 4:36 PM, Geoffrey Irving <irving@naml.us> wrote:
Show 12 quoted lines
> Added cached-sha-map.[hc] implementing a persistent hash map from sha1 to sha1.
> The map is read with mmap, and completely rewritten if any entries change.  It
> would be good to add incremental update to handle the usual case where only a
> few entries change.
>
> This structure is used by patch-ids.c to cache the mapping from commit to
> patch-id into $GIT_DIR/patch-id-cache.  In the one case I've tested so far,
> this speeds up the second invocation of git-cherry by two orders of magnitude.
>
> Original code cannibalized from Johannes Schindelin's notes-index structure.
>
> <snip>
Forgot to cc people from previous threads.

Is starting a new thread each time I update a patch the correct way to do things?

Geoffrey
Previous: Geoffrey IrvingNext: Johannes Schindelin
Message 2 of 4 in “cherry: cache commit to patch-id pairs to avoid repeating work”
  1. cherry: cache commit to patch-id pairs to avoid repeating workGeoffrey Irving, Jun 7, 2008
  2. Geoffrey IrvingJun 8, 2008
  3. Johannes SchindelinJun 8, 2008
  4. Johannes SchindelinJun 8, 2008

Read the whole thread, see it on lore, or plain text.

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