Re: GSOC on designing a faster index format

From: Thomas Rast <trast@student.ethz.ch>
Date: Mar 21, 2012, 22:20 UTC
Message-ID: <87y5qtmw8l.fsf@thomas.inf.ethz.ch>
In-Reply-To: <CAAQUJYbr+RbcpRzKqK+s+9sXezQuFR-S=OdSdnTYTtURDqKRhQ@mail.gmail.com>

Hi Calvin,

Please also read/follow the other threads on the same topic

  http://thread.gmane.org/gmane.comp.version-control.git/193541
  http://thread.gmane.org/gmane.comp.version-control.git/193550

Calvin Deutschbein <deutschbeinc@gmail.com> writes:

Show 6 quoted lines

> Verifying
> correctness, it would seem, can generally be done without a rewrite
> and isn't necessarily exhaustively necessary with every index edit if
> efficiency is becoming of utmost concern.  This then, would seem to
> indicate that hashing the index wouldn't always be necessary.  Is it
> done then just for 100% security in index correctness?

It's basically the *easiest* way to make sure the index was not corrupted. It also happens to be plenty fast enough for not-so-big projects.

Show 6 quoted lines

> I also appreciate the later mention of the importance of being as easy
> to parse as possible, as I tend to find such coding an intellectually
> engaging exercise and this represents a valid reason to invest
> resources in such a pursuit.  Unfortunately, I'm not entirely familiar
> with other git-reading programs.  Is there a specific set of such
> programs I should look into?

At least jgit and libgit2, the former because it represents a large user base (more or less everybody using Eclipse and/or Gerrit) and the latter because their life is already hard enough with the current git internals ;-)

-- 
Thomas Rast
trast@{inf,student}.ethz.ch