Test the current state of the cache-tree optimization
authorThomas Rast <trast@student.ethz.ch>
Tue, 6 Dec 2011 17:43:36 +0000 (18:43 +0100)
committerJunio C Hamano <gitster@pobox.com>
Tue, 6 Dec 2011 22:53:13 +0000 (14:53 -0800)
commit4eb0346fb8f8a59a1fb7a6bd01154655a7020087
tree263a7a1b8ca77a78f5f8b87c35dd81861c11af39
parent1aed2fe394f45fed7b97e268cfa11d25c3d8da27
Test the current state of the cache-tree optimization

The cache-tree optimization originally helped speed up write-tree
operation.  However, many commands no longer properly maintain -- or
use an opportunity to cheaply generate -- the cache-tree data.  In
particular, this affects commit, checkout and reset.  The notable
examples that *do* write cache-tree data are read-tree and write-tree.

This sadly means most people no longer benefit from the optimization,
as they would not normally use the plumbing commands.

Document the current state of affairs in a test file, in preparation
for improvements in the area.

Signed-off-by: Thomas Rast <trast@student.ethz.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t0090-cache-tree.sh [new file with mode: 0755]