git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC] Designing a faster index format - Progress Report week 8

From
Thomas Rast <trast@student.ethz.ch>
Date
Jun 15, 2012, 13:39 UTC
Message-ID
<878vfo1you.fsf@thomas.inf.ethz.ch>
In-Reply-To
<20120611205312.GB18686@tgummerer>
Thomas Gummerer <t.gummerer@gmail.com> writes:
Show 5 quoted lines
> == 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
Previous: Thomas Gummerer
Message 2 of 2 in “[GSoC] Designing a faster index format - Progress Report week 8”
  1. Thomas GummererJun 11, 2012
  2. Thomas RastJun 15, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.