Re: [PATCH] Cache stat_tracking_info() for faster status and branch -v

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Oct 20, 2012, 09:02 UTC
Message-ID: <CACsJy8A2ub2y64qAbP2OTPNsVi-KmxAMFdwBBLXYReF5ASZLKg@mail.gmail.com>
In-Reply-To: <7v7gqmjl6n.fsf@alter.siamese.dyndns.org>

On Sat, Oct 20, 2012 at 2:50 AM, Junio C Hamano <gitster@pobox.com> wrote:

> Not particularly interested in the cause, but not so strongly
> against it to veto it.

I wonder how many people keep old branches like I do, which are usually far from remotes.

Show 11 quoted lines

> Doesn't it make more sense to use a notes-cache that is keyed off of
> the commit object name X of the remote?  You will have a single note
> that stores a blob for the commit object remotes/origin/master, and
> the blob tells you how far the commit at the tip of 'frotz' is from
> it, and the same for 'xyzzy'.
>
> You would obviouly need to run "gc" on such a notes-cache tree from
> time to time, removing notes for commits that are not tip of any
> branch that could be a fork point, and from the remaining notes
> blobs, entries that describe commits that are not tip of any branch,
> if you go that route.

The notes-cache route looks much nicer. Thanks. We can also use Jeff's persistent hash table from his rename-cache series.

-- 
Duy