Re: [GSoC] Designing a faster index format

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 21, 2012 at 4:22 PM, Thomas Gummerer <t.gummerer@xxxxxxxxx> wrote:
>
> On Mar 21, 2012, at 2:29 AM, Nguyen Thai Ngoc Duy wrote:
>
>> On Wed, Mar 21, 2012 at 4:17 AM, Thomas Gummerer <t.gummerer@xxxxxxxxx> wrote:
>>> There are some questions I would have about the project.
>>> Has there already been any development or thoughts in that direction?
>>
>> Tree-based format seems to be favored by core developers, for example
>> in the footnote in [1]. But there have been no attempts to realize it.
>> You may want to search mail archive for more.
>>
>
> Thanks for your answer, so I would probably implement a tree based structure.

There may be a better approach, maybe a simple database format that we
could immitate. It's up to you to find out :)

> However I got one more question, since I'm not yet really familiar with the
> code and internal structure of git, what exactly does the SHA1 over the
> index exactly achieve? Is it only for checking if the index is still correct
> for the next time it is used and has not been changed or is there a more
> important function of it?

It makes sure the index is not corrupt (by disk faults for example). I
don't think it is used for anything else. Cheaper checksum can be used
if good enough for the index. See
http://thread.gmane.org/gmane.comp.version-control.git/190016 and the
following reply.
-- 
Duy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]