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

Re: [GSoC] Designing a faster index format - Progress report week 13

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 16, 2012, 20:46 UTC
Message-ID
<7vwr23zb65.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20120716203300.GA1849@tgummerer.surfnet.iacbox>
Thomas Gummerer <t.gummerer@gmail.com> writes:
Show 8 quoted lines
> == Work done in the previous 12 weeks ==
>
> - Definition of a tentative index file v5 format [1]. This differs
>   from the proposal in making it possible to bisect the directory
>   entries and file entries, to do a binary search. The exact bits
>   for each section were also defined. To further compress the index,
>   along with prefix compression, the stat data is hashed, since
>   it's only used for comparison, but the plain data is never used.
s/comparison/equality comparison/ perhaps?
>   Thanks to Michael Haggerty, Nguyen Thai Ngoc Duy, Thomas Rast
>   and Robin Rosenberg for feedback.
> - Read the index format format and translate it to the current in
s/format format/on-disk file format/ or something?
>   memory format. This doesn't include reading any of the current
>   extensions, which are now part of the main index. The code again
>   is on github. [4] Thanks for reviewing the first steps to Thomas
>   Rast.
Show 7 quoted lines
> - Started implementing the writer, which extracts the directories from
>   the in-memory format, and writes the header and the directories to
>   disk.
> - I found a few bugs in the algorithm for extracting the directories
>   and decided to completely rewrite it, using a hash table instead of
>   simple lists, since the old one would have to many corner cases to
>   handle.

What does "the algorithm" refer to? Is it the one described in the previous bullet point, or is it the code in production? If latter, it would help to separate out the task to fix the breakage, as people with the current or previous versions of Git will be negatively affected until that bug is fixed. If former, I am not sure if this task needs to be described in two bullet points ("I did X, X had bug so I redid X in a different way" is still a single task to do X).

> == Work done int the last week ==
>
> - Polished the patch for the ce_namelen field. The thread for the
>   patch can be found at [5].

Thanks for this one; I think it is ready for 'next', but if you are still not satisfied I do not mind waiting for further perfection.

Previous: Thomas GummererNext: Thomas Gummerer
Message 2 of 12 in “[GSoC] Designing a faster index format - Progress report week 13”
  1. Thomas GummererJul 16, 2012
  2. Junio C HamanoJul 16, 2012
  3. Thomas GummererJul 17, 2012
  4. Thomas GummererJul 17, 2012
  5. Robin RosenbergJul 22, 2012
  6. Junio C HamanoJul 22, 2012
  7. Thomas RastJul 22, 2012
  8. Junio C HamanoJul 22, 2012
  9. Robin RosenbergJul 23, 2012
  10. Thomas RastJul 24, 2012
  11. Junio C HamanoJul 24, 2012
  12. Thomas RastJul 25, 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.