== Work done in the previous 13 weeks ==
- Definition of a tentative index file v5 format . 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 equality comparison, but the plain data is
Thanks to Michael Haggerty, Nguyen Thai Ngoc Duy, Thomas Rast
and Robin Rosenberg for feedback.
- Prototype of a converter from the index format v2/v3 to the index
format v5.  The converter reads the index from a git repository,
can output parts of the index (header, index entries as in
git ls-files --debug, cache tree as in test-dump-cache-tree, or
the reuc data). Then it writes the v5 index file format to
.git/index-v5. Thanks to Michael Haggerty for the code review.
- Prototype of a reader for the new index file format.  The
reader has mainly the purpose to show the algorithm used to read
the index lexicographically sorted after the full name which is
required by the current internal memory format. Big thanks for
reviewing this code and giving me advice on refactoring goes
to Michael Haggerty.
- Read the on-disk index file format and translate it to the current
in 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.  Thanks for reviewing the first steps to Thomas
- Read the cache-tree data (formerly an extension, now it's integrated
with the rest of the directory data) from the new ondisk format.
There are still a few optimizations to do in this algorithm.
- Started implementing the API (suggested by Duy), but it's still
in the very early stages. There is one commit for this on GitHub ,
but it's a very early work in progress.
- Started implementing the writer, which extracts the directories from
the in-memory format, and writes the header and the directories to
disk. The algorithm uses a hash-table instead of a simple list,
to avoid many corner cases.
- Implemented writing the file block to disk, and basic tests from the
test suite are running fine, not including tests that require
conflicted data or the cache-tree to work, which both are not
- Started implementing a patch to introduce a ce_namelen field in
struct cache_entry and drop the name length from the flags. 
Thanks to Junio, Duy and Thomas for reviews and suggestions for
- Implemented the cache-tree and conflict data writing to the
== Work done in the last week ==
- Fixed a few bugs in cache-tree and conflict writing in my index-v5
- I visited Thomas in Zuerich this weekend, as some of you may
have noticed on the mailing list, thanks a lot for the
hospitality. And thanks also to Tomas for the company on saturday
- With the help of Thomas I fixed the resolve undo data writing,
and a couple more bugs in my code, so that the test suite passes
with INDEX_VERSION_DEFAULT = 5.
- We added a POC, for partial loading in git grep. This is still a
pretty hacky implementation, but it demonstrates pretty well
how much can be gained. Here are the timings Thomas posted on
IRC yesterday. The improvements of ls-files are not drastic
compared to index-v4, but git greps in subdirs benefit a lot
from partial loading.
Test this tree
0002.2: v: ls-files 0.13(0.11+0.02)
0002.3: v: grep nonexistent -- subdir 0.12(0.10+0.02)
0002.5: v4: ls-files 0.11(0.09+0.01)
0002.6: v4: grep nonexistent -- subdir 0.10(0.08+0.02)
0002.8: v5: ls-files 0.10(0.07+0.02)
0002.9: v5: grep nonexistent -- subdir 0.01(0.00+0.00)
- All changes again are in my repository on github, in case someone
wants to try them out. 
== Outlook for the next week ==
- Refactoring of the code. There are still some code smells in the
current code, which need to be refactored.
- There are also still some possible optimizations for the code,
which will be included.
- I'll also bring the reader up to date again, and make it possible
for it to update a single index entry, to test the implementation
of rereading a entry when the crc is wrong (for the future partial
write, both writer and reader side still have to be implemented).
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html