From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Mon, 01 Oct 2012 05:16:34 GMT
Subject: Re: Commit cache to speed up rev-list and merge
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