Re: Git's database structure

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Sep 6, 2007, 12:56 UTC
Message-ID: <Pine.LNX.4.64.0709061354180.28586@racer.site>
In-Reply-To: <9e4733910709050912i57ed7137o6abb02ee741d394b@mail.gmail.com>

Hi,

On Wed, 5 Sep 2007, Jon Smirl wrote:

Show 13 quoted lines

> On 9/5/07, Julian Phillips <julian@quantumfyre.co.uk> wrote:
> > On Wed, 5 Sep 2007, Jon Smirl wrote:
> >
> > >> Ah, there we go. A use-case at last :)
> >
> > But not a brilliant one.  You sign off on commits not blobs.  So you 
> > go from the sign-off to paths, then to blobs.  There is no need to go 
> > from blob to path unless you deliberately introduce such a need.
> 
> Use blame for an example. Blame has to crawl every commit to see if it 
> touched the file. It keeps doing this until it figures out the last 
> author for every line in the file. Worse case blame has to crawl every 
> commit in the data store.

But you can add _yet another_ index to it, which can be generated on the fly, so that Git only has to generate the information once, and then reuse it later. As a benefit of this method, the underlying well-tested structure needs no change at all.

BTW could you please, please, please cut the quoted message that you are _not_ responding to? It really _wastes_ my time.

Ciao, Dscho