git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Thomas Rast <trast@student.ethz.ch>, Jeff King <peff@peff.net>,
	git@vger.kernel.org
Subject: Re: [git wiki PATCH 2/3] "Designing a faster index format" project
Date: Sat, 3 Mar 2012 10:30:17 +0700	[thread overview]
Message-ID: <CACsJy8DWKaZZfp4kyj3bkBVF3yzzFa24uMDfoxVc=ATWs1uRew@mail.gmail.com> (raw)
In-Reply-To: <7vobseeu9i.fsf@alter.siamese.dyndns.org>

On Sat, Mar 3, 2012 at 1:24 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Having harder and more ambitious ones in the mix is OK, but I suspect this
> one is probably a bit too ambitious to be realistic for a student project
> that lasts only 3 months.
>
> This proposal is about a change that touches core parts of the system that
> has the chance of inflicting permanent damage to end users' histories.
> I'd have a hard time reviewing and convincing myself that the change is
> good, if such a change were done by somebody new to the system, even if
> the work were mentored very closely by one of our top 15 committers.

I was comparing the excitement of seeing this implemented vs packv4,
then realised the complexity of work may be more or less the same.
But, if the new format is not mmap'd for direct access, we can
reconstruct "struct cache_entry*" exactly as it is now from new
format. That makes it less sensitive to the core parts and we still
hopefully benefit from new format (mostly I/O I guess). Phase 2 could
come later to make core parts aware of new format.
-- 
Duy

  reply	other threads:[~2012-03-03  3:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  9:11 GSoC 2012 application process Jeff King
2012-03-02 11:05 ` [git wiki PATCH 1/3] "Improving parallelism in various commands" project Thomas Rast
2012-03-02 11:05   ` [git wiki PATCH 2/3] "Designing a faster index format" project Thomas Rast
2012-03-02 11:08     ` Jeff King
2012-03-02 18:24     ` Junio C Hamano
2012-03-03  3:30       ` Nguyen Thai Ngoc Duy [this message]
2012-03-02 11:05   ` [git wiki PATCH 3/3] "Improving the `git add -p` interface" project Thomas Rast
2012-03-02 14:29   ` [git wiki PATCH 1/3] "Improving parallelism in various commands" project Nguyen Thai Ngoc Duy
2012-03-02 17:35   ` James Pickens
2012-03-02 14:52 ` GSoC 2012 application process Nguyen Thai Ngoc Duy
2012-03-02 21:48 ` Junio C Hamano
2012-03-03  0:09   ` Jeff King
2012-03-03 21:14 ` [git wiki PATCH] "Modernizing and expanding Git.pm" project Jakub Narebski
2012-03-03 22:23   ` Jeff King
2012-03-04 23:35 ` [git wiki PATCH] Teaching "--3way" to "git apply" Junio C Hamano
2012-03-05  5:33   ` Jeff King
2012-03-05  8:05     ` Thomas Rast
2012-03-05 10:02       ` Jeff King
2012-03-05 13:38 ` GSoC 2012 application process Matthieu Moy
2012-03-05 13:58   ` Jeff King
2012-03-05 14:42     ` Matthieu Moy
2012-03-05 23:53       ` Jeff King
2012-03-07 14:36 ` GSoC backup admin Jeff King
2012-03-07 15:27   ` Shawn Pearce
2012-03-08 21:18 ` [gsoc2012 wiki PATCH] "Use JavaScript library / framework in gitweb" project Jakub Narebski
2012-03-09  7:24   ` Jeff King
2012-03-10  0:46 ` [gsoc2012 wiki PATCH] "`git instaweb --serve`" project Jakub Narebski
2012-03-11 22:30 ` [gsoc2012 wiki PATCH] "Graphical diff in git-gui" project Jakub Narebski

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACsJy8DWKaZZfp4kyj3bkBVF3yzzFa24uMDfoxVc=ATWs1uRew@mail.gmail.com' \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).