From: Thomas Rast <trast@student.ethz.ch>
To: Thomas Gummerer <t.gummerer@gmail.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>, <git@vger.kernel.org>
Subject: Re: [GSoC] Designing a faster index format
Date: Wed, 21 Mar 2012 13:51:10 +0100 [thread overview]
Message-ID: <871uomrubl.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <CACsJy8D2RwG-Nr5btcQj0f9=JACvH6mf7LNi=Jnb_y+j4_2u0A@mail.gmail.com> (Nguyen Thai Ngoc Duy's message of "Wed, 21 Mar 2012 17:34:15 +0700")
Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
> On Wed, Mar 21, 2012 at 4:22 PM, Thomas Gummerer <t.gummerer@gmail.com> wrote:
>>
>> On Mar 21, 2012, at 2:29 AM, Nguyen Thai Ngoc Duy wrote:
>>
>> 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.
Note that switching the checksum used already requires a
backwards-incompatible change of the index format. If we are going to
do that, I'm somewhat opposed to not also revising it along the lines
sketched by Shawn (at least).
See my reply to Elton Sky
http://thread.gmane.org/gmane.comp.version-control.git/193550/focus=193571
for links to some threads you may want to look at.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-03-21 12:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 21:17 [GSoC] Designing a faster index format Thomas Gummerer
2012-03-21 1:29 ` Nguyen Thai Ngoc Duy
2012-03-21 9:22 ` Thomas Gummerer
2012-03-21 10:34 ` Nguyen Thai Ngoc Duy
[not found] ` <CALgYhfPOJpKbM__iU4KvChWeXWyyhWb2ocR-SLvrQQHNw5F5dQ@mail.gmail.com>
2012-03-21 11:18 ` Nguyen Thai Ngoc Duy
2012-03-21 12:51 ` Thomas Rast [this message]
2012-03-21 15:43 ` Thomas Gummerer
2012-03-21 16:19 ` Thomas Rast
2012-03-22 22:51 ` Thomas Gummerer
2012-03-23 10:10 ` Thomas Rast
2012-03-25 1:28 ` Thomas Gummerer
2012-03-26 20:35 ` Thomas Gummerer
2012-03-26 21:14 ` Junio C Hamano
2012-03-27 11:08 ` Thomas Gummerer
2012-03-27 11:47 ` Thomas Rast
2012-03-29 15:21 ` Thomas Gummerer
2012-03-29 21:06 ` Junio C Hamano
2012-03-30 5:19 ` Nguyen Thai Ngoc Duy
2012-04-02 21:02 ` Thomas Gummerer
2012-04-03 8:51 ` Michael Haggerty
2012-04-03 12:28 ` Nguyen Thai Ngoc Duy
2012-04-03 19:07 ` Thomas Gummerer
2012-04-03 20:15 ` david
2012-04-04 20:05 ` Thomas Gummerer
2012-04-05 14:39 ` Noel Grandin
2012-04-05 21:49 ` Thomas Rast
2012-04-06 3:22 ` Shawn Pearce
2012-04-06 15:11 ` Nguyen Thai Ngoc Duy
2012-04-06 15:24 ` Thomas Rast
2012-04-06 15:44 ` Nguyen Thai Ngoc Duy
2012-04-06 17:13 ` Shawn Pearce
2012-04-06 17:23 ` Nguyen Thai Ngoc Duy
2012-04-06 17:56 ` Shawn Pearce
[not found] ` <878vi18eqd.fsf@thomas.inf.ethz.ch>
[not found] ` <83571955-9256-4032-9182-FA9062D28B9D@gmail.com>
[not found] ` <8D2805A4-9C5F-43A9-B3ED-0DB77341A03C@gmail.com>
2012-04-19 10:49 ` Nguyen Thai Ngoc Duy
[not found] ` <877gxcoron.fsf@thomas.inf.ethz.ch>
2012-04-20 20:02 ` Jeff King
2012-04-05 10:43 ` Michael Haggerty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871uomrubl.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=t.gummerer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).