Re: What's cooking in git.git (Dec 2009, #03; Tue, 08)

>  (merged to 'next' on 2009-11-25 at 71380f5)
>  + tests: rename duplicate t1009
>  (merged to 'next' on 2009-11-23 at f712a41)
>  + sparse checkout: inhibit empty worktree
>  + Add tests for sparse checkout
>  + read-tree: add --no-sparse-checkout to disable sparse checkout support
>  + unpack-trees(): ignore worktree check outside checkout area
>  + unpack_trees(): apply $GIT_DIR/info/sparse-checkout to the final index
>  + unpack-trees(): "enable" sparse checkout and load $GIT_DIR/info/sparse-checkout
>  + unpack-trees.c: generalize verify_* functions
>  + unpack-trees(): add CE_WT_REMOVE to remove on worktree alone
>  + Introduce "sparse checkout"
>  + dir.c: export excluded_1() and add_excludes_from_file_1()
>  + excluded_1(): support exclude files in index
>  + unpack-trees(): carry skip-worktree bit over in merged_entry()
>  + Read .gitignore from index if it is skip-worktree
>  + Avoid writing to buffer in add_excludes_from_file_1()
>  + Teach Git to respect skip-worktree bit (writing part)
>  + Teach Git to respect skip-worktree bit (reading part)
>  + Introduce "skip-worktree" bit in index, teach Git to get/set this bit
>  + Add test-index-version
>  + update-index: refactor mark_valid() in preparation for new options
>
> There were some test glitches reported and at least one test seems to
> be broken in the sense that it is not testing what it is trying to.
> Fix-up expected.