From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: elton sky <eltonsky9404@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Thomas Rast <trast@student.ethz.ch>
Subject: Re: GSoC - Designing a faster index format
Date: Sat, 24 Mar 2012 15:58:46 +0700 [thread overview]
Message-ID: <CACsJy8C=4WaN4MZrZMaD3FqZrF2jCP5sm0F0SpDvzQnYfka9Ew@mail.gmail.com> (raw)
In-Reply-To: <CAKTdtZmLOzAgG0uCDcVr+O41XPX-XnoVZjsZWPN-BLjq2oG-7A@mail.gmail.com>
On Sat, Mar 24, 2012 at 2:50 PM, elton sky <eltonsky9404@gmail.com> wrote:
> Thanks again Nguyen,
>
>> Which reminds me, we cannot abandon current index format. Users should
>> be allowed to choose which format to use. It may be hard to keep the
>> code support two formats while still taking advantage of the new one.
>> Maybe you could internally convert old format to new one in memory so
>> that git code only has to deal with one format, but that adds more
>> cost on using old format. I don't know..
>
> I understand we should allow user to switch between old & new format.
> But I guess that should only happens when user init a working dir,
> isn't it? Otherwise I have to transform them back n forth. If a user
> chooses to use old format, I assume their repository is not large, so
> there should not be big delay for new format.
Users may choose to stick with old format because other git tools rely
on that (or they want to use older git versions at the same time).
Note that current index works "fine" with ~50k files in working
directory. Not huge, but not small either. Overhead on old format
should be reasonable.
--
Duy
next prev parent reply other threads:[~2012-03-24 8:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 23:10 GSoC - Designing a faster index format elton sky
2012-03-21 1:18 ` Nguyen Thai Ngoc Duy
2012-03-21 11:25 ` Thomas Rast
2012-03-21 12:01 ` elton sky
2012-03-22 20:32 ` elton sky
2012-03-23 0:46 ` Jakub Narebski
2012-03-23 1:30 ` Nguyen Thai Ngoc Duy
2012-03-23 10:27 ` elton sky
2012-03-23 11:24 ` Nguyen Thai Ngoc Duy
[not found] ` <CAKTdtZmLOzAgG0uCDcVr+O41XPX-XnoVZjsZWPN-BLjq2oG-7A@mail.gmail.com>
2012-03-24 8:58 ` Nguyen Thai Ngoc Duy [this message]
[not found] ` <CAKTdtZkpjVaBSkcieojKj+V7WztT3UDzjGfXyghY=S8mq+X9zw@mail.gmail.com>
[not found] ` <CACsJy8D85thmK_5jLC7MxJtsitLr=zphKiw2miwPu7Exf7ty=Q@mail.gmail.com>
2012-03-26 12:36 ` elton sky
2012-03-26 12:41 ` elton sky
2012-03-26 14:28 ` Thomas Rast
2012-03-26 15:25 ` Nguyen Thai Ngoc Duy
2012-03-26 16:08 ` Shawn Pearce
2012-03-27 2:49 ` elton sky
2012-03-27 3:34 ` David Barr
2012-03-27 6:33 ` Nguyen Thai Ngoc Duy
2012-03-29 9:45 ` Jeff King
2012-03-27 6:31 ` Nguyen Thai Ngoc Duy
2012-03-26 16:19 ` Nguyen Thai Ngoc Duy
2012-03-27 3:20 ` elton sky
2012-03-27 6:43 ` Nguyen Thai Ngoc Duy
2012-04-02 11:50 ` elton sky
2012-04-02 12:31 ` Nguyen Thai Ngoc Duy
2012-04-02 14:27 ` Shawn Pearce
2012-04-02 15:12 ` Nguyen Thai Ngoc Duy
2012-04-04 8:26 ` elton sky
2012-04-04 12:20 ` Nguyen Thai Ngoc Duy
2012-04-04 16:22 ` elton sky
2012-04-06 3:13 ` elton sky
2012-04-06 3:15 ` elton sky
2012-04-07 8:29 ` elton sky
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='CACsJy8C=4WaN4MZrZMaD3FqZrF2jCP5sm0F0SpDvzQnYfka9Ew@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=eltonsky9404@gmail.com \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/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.