git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Thomas Gummerer <t.gummerer@gmail.com>
Cc: <git@vger.kernel.org>, <gitster@pobox.com>,
	<mhagger@alum.mit.edu>, <pclouds@gmail.com>
Subject: Re: [GSoC] Designing a faster index format - Progress Report week 8
Date: Fri, 15 Jun 2012 15:39:45 +0200	[thread overview]
Message-ID: <878vfo1you.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <20120611205312.GB18686@tgummerer> (Thomas Gummerer's message of "Mon, 11 Jun 2012 22:53:12 +0200")

Thomas Gummerer <t.gummerer@gmail.com> writes:

> == Outlook for the next week ==
>
> - Continue implementing the API as discussed on [5].
>
> [5] http://thread.gmane.org/gmane.comp.version-control.git/198283/focus=198474

Sorry for being rather slow this week!  I still intend to do another
review of the github code RSN, however I felt I should point out some
more IRC conclusions to the list.

I talked Thomas out of going forward with the API as the next step, and
instead work towards having a writer side for the current format.

This should have some benefits:

* The code becomes more easily testable, and hopefully able to run the
  test suite.

* Spelling the writer in code should shake down any unforeseen
  deficiencies of the format.

  Until update-index or similar learn to use the partial writing
  facilities, we should have a little extra tool here that allows poking
  at a single entry for testing.

* The API will need to have an updating and a writing side, and what
  that should look like will become clearer.

That does mean that the API-demo in git-ls-files (suggested by Duy) will
likely have to wait until after midterms.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

      reply	other threads:[~2012-06-15 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 20:53 [GSoC] Designing a faster index format - Progress Report week 8 Thomas Gummerer
2012-06-15 13:39 ` Thomas Rast [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=878vfo1you.fsf@thomas.inf.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mhagger@alum.mit.edu \
    --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).