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

Re: Commit cache to speed up rev-list and merge

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Oct 1, 2012, 05:16 UTC
Message-ID
<CACsJy8CQaOw9aUJDAoG+gg_n0=A-62KdwYukf-MbgXwCigr8xA@mail.gmail.com>
In-Reply-To
<CAJo=hJsGptu8c04XQh0xLmMhz+mxYKAOQfhbjaNK887dY-jAMA@mail.gmail.com>
On Mon, Oct 1, 2012 at 9:27 AM, Shawn Pearce <spearce@spearce.org> wrote:
> Git has enough magic switches. It doesn't need yet another magic
> switch that one group of users needs to set, and another can safely
> ignore because their project's usage just happens to align with Linus
> Torvald's current world view.

I see it as tuning, not switching. It's like setting the number of commits where bitmaps are taken. We can see the commit cache as a table, where columns are commit properties. We have a column for date, one for the first parent. Users can choose to have a third column for the second parent, or another one for root tree sha-1. The implementation could be made generic to support caching any <n> sha1-columns.

-- 
Duy
Previous: Shawn Pearce
Message 10 of 10 in “Re: Commit cache to speed up rev-list and merge”
  1. Shawn PearceSep 27, 2012
  2. Jeff KingSep 27, 2012
  3. Shawn PearceSep 27, 2012
  4. Jeff KingSep 27, 2012
  5. Nguyen Thai Ngoc DuySep 28, 2012
  6. Nguyen Thai Ngoc DuySep 28, 2012
  7. Shawn PearceOct 1, 2012
  8. Nguyen Thai Ngoc DuyOct 1, 2012
  9. Shawn PearceOct 1, 2012
  10. Nguyen Thai Ngoc DuyOct 1, 2012

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.