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

Re: [PATCH] Adding a cache of commit to patch-id pairs to speed up git-cherry

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 2, 2008, 16:18 UTC
Message-ID
<alpine.DEB.1.00.0806021717130.13507@racer.site.net>
In-Reply-To
<7f9d599f0806020849g567461b2kecd65dbd35d3dc3b@mail.gmail.com>
Hi,
On Mon, 2 Jun 2008, Geoffrey Irving wrote:
Show 11 quoted lines
> On Mon, Jun 2, 2008 at 8:37 AM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>
> > Another issue that just hit me: this cache is append-only, so if it 
> > grows too large, you have no other option than to scratch and recreate 
> > it. Maybe this needs porcelain support, too?  (git gc?)
> 
> If so, the correct operation is to go through the hash and remove 
> entries that refer to commits that no longer exist.  I can add this if 
> you want.  Hopefully somewhere along the way git-gc constructs an easy 
> to traverse list of extant commits, and this will be straightforward.

I don't know... if you have created a cached patch-id for every commit (by mistake, for example) and do not need it anymore, it might make git-cherry substantially faster to just scrap the cache.

Hrm, Dscho

Previous: Shawn O. PearceNext: Geoffrey Irving
Message 8 of 16 in “Adding a cache of commit to patch-id pairs to speed up git-cherry”
  1. Adding a cache of commit to patch-id pairs to speed up git-cherryGeoffrey Irving, Jun 2, 2008
  2. Johannes SchindelinJun 2, 2008
  3. Jeff KingJun 2, 2008
  4. Geoffrey IrvingJun 2, 2008
  5. Johannes SchindelinJun 2, 2008
  6. Geoffrey IrvingJun 2, 2008
  7. Shawn O. PearceJun 2, 2008
  8. Johannes SchindelinJun 2, 2008
  9. Geoffrey IrvingJun 2, 2008
  10. Johannes SchindelinJun 2, 2008
  11. Geoffrey IrvingJun 7, 2008
  12. Johannes SchindelinJun 8, 2008
  13. Geoffrey IrvingJun 2, 2008
  14. Johannes SchindelinJun 2, 2008
  15. Geoffrey IrvingJun 2, 2008
  16. Johannes SchindelinJun 2, 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.