From: Thomas Rast <trast@inf.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 17:19:15 +0100 [thread overview]
Message-ID: <871uomq64c.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <8901F6B5-7396-44E1-9687-20BF95114728@gmail.com> (Thomas Gummerer's message of "Wed, 21 Mar 2012 16:43:15 +0100")
Thomas Gummerer <t.gummerer@gmail.com> writes:
> While reworking the index into a tree (not to mention if it's in database format),
> the backward compatibility would be broken anyway from what I understood?
> Therefore taking Shawns thoughts into account should not be a lot more work
> and should make it also easier to implement for the .git reading programs,
> since it's easier to parse for the core it should also be easier to parse for them.
>
> Then if changing the checksum algorithm can bring some advantage I think
> it should be well worth the extra work while we break compatibility in any case.
AFAICS we are in agreement. I was saying it's not worth breaking
compatibility for *only* the checksum change. You are coming from the
other side: "once all the rest is done, the checksum change is easy",
which is probably true.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-03-21 16:19 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
2012-03-21 15:43 ` Thomas Gummerer
2012-03-21 16:19 ` Thomas Rast [this message]
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=871uomq64c.fsf@thomas.inf.ethz.ch \
--to=trast@inf.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.