From: Junio C Hamano <gitster@pobox.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: Thomas Gummerer <t.gummerer@gmail.com>, <git@vger.kernel.org>,
<mhagger@alum.mit.edu>, Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Subject: Re: [GSoC] Designing a faster index format - Progress report
Date: Tue, 29 May 2012 11:33:59 -0700 [thread overview]
Message-ID: <7vzk8q4z1k.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <87vcjfi09m.fsf@thomas.inf.ethz.ch> (Thomas Rast's message of "Tue, 29 May 2012 15:29:09 +0200")
Thomas Rast <trast@student.ethz.ch> writes:
> Then I will twist Duy's words to mean that you should make git-ls-files
> the poster child of this new API for development and profiling purposes
> :-)
Exactly.
> Actually converting the rest of the git code base to such an API is too
> big an undertaking for the summer, so please don't stray on that path.
Didn't I say that this topic is too big for a GSoC task _way_ before
GSoC organization application started? Without meaningful portion
of the codebase using the newly proposed data stracture and giving
demonstratably better performance figure, it is very hard to justify
that the project completed successfully at the end of the summer.
prev parent reply other threads:[~2012-05-29 18:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 12:21 [GSoC] Designing a faster index format - Progress report Thomas Gummerer
2012-05-24 20:01 ` Thomas Rast
2012-05-24 20:57 ` Junio C Hamano
2012-05-25 11:31 ` Nguyen Thai Ngoc Duy
2012-05-25 20:15 ` Thomas Gummerer
2012-05-26 4:09 ` Nguyen Thai Ngoc Duy
2012-05-27 9:04 ` Thomas Gummerer
2012-05-27 9:27 ` Junio C Hamano
2012-05-27 12:23 ` Nguyen Thai Ngoc Duy
2012-05-28 8:26 ` Thomas Gummerer
2012-05-29 13:29 ` Thomas Rast
2012-05-29 13:43 ` Nguyen Thai Ngoc Duy
2012-05-29 18:33 ` Junio C Hamano [this message]
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=7vzk8q4z1k.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=pclouds@gmail.com \
--cc=t.gummerer@gmail.com \
--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 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).