Re: What's cooking in git.git (Jun 2014, #06; Thu, 26)

From: Duy Nguyen <pclouds@gmail.com>
Date: Jun 29, 2014, 00:33 UTC
Message-ID: <CACsJy8CXLO2Tt_poChMkT7CPyUaY4gbF1cdsscDH3LsUaJRxPA@mail.gmail.com>
In-Reply-To: <xmqqvbrn2utv.fsf@gitster.dls.corp.google.com>

On Fri, Jun 27, 2014 at 5:02 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 35 quoted lines

> * nd/split-index (2014-06-13) 32 commits
>  - t1700: new tests for split-index mode
>  - t2104: make sure split index mode is off for the version test
>  - read-cache: force split index mode with GIT_TEST_SPLIT_INDEX
>  - read-tree: note about dropping split-index mode or index version
>  - read-tree: force split-index mode off on --index-output
>  - rev-parse: add --shared-index-path to get shared index path
>  - update-index --split-index: do not split if $GIT_DIR is read only
>  - update-index: new options to enable/disable split index mode
>  - split-index: strip pathname of on-disk replaced entries
>  - split-index: do not invalidate cache-tree at read time
>  - split-index: the reading part
>  - split-index: the writing part
>  - read-cache: mark updated entries for split index
>  - read-cache: save deleted entries in split index
>  - read-cache: mark new entries for split index
>  - read-cache: split-index mode
>  - read-cache: save index SHA-1 after reading
>  - entry.c: update cache_changed if refresh_cache is set in checkout_entry()
>  - cache-tree: mark istate->cache_changed on prime_cache_tree()
>  - cache-tree: mark istate->cache_changed on cache tree update
>  - cache-tree: mark istate->cache_changed on cache tree invalidation
>  - unpack-trees: be specific what part of the index has changed
>  - resolve-undo: be specific what part of the index has changed
>  - update-index: be specific what part of the index has changed
>  - read-cache: be specific what part of the index has changed
>  - read-cache: be strict about "changed" in remove_marked_cache_entries()
>  - read-cache: store in-memory flags in the first 12 bits of ce_flags
>  - read-cache: relocate and unexport commit_locked_index()
>  - read-cache: new API write_locked_index instead of write_index/write_cache
>  - sequencer: do not update/refresh index if the lock cannot be held
>  - ewah: delete unused ewah_read_mmap_native declaration
>  - ewah: fix constness of ewah_read_mmap
>
>  What's the doneness of this one?

It's done, at least for the extension format and core algorithm. Later we may want to automatically re-split the index when too many changes are accumulated in the main index.

-- 
Duy