Junio C Hamano <gitster@xxxxxxxxx> writes: >> While write-tree has code to write out the cache-tree information >> (since we have to compute it anyway if the cache is stale), commit >> lost this capability when it became a builtin and moved away from >> using write-tree. > > Earlier the code read from the index, made sure that it is not unmerged by > running cache_tere_update(), before running prepare-commit-msg hook. The > hook used to see the index that was read in this codepath which is the > same as what pre-commit left us. > > Why run an extra I/O here? The index file could be quite large, and I do > not want people to writing it out without good reason. One possible good reason is if you did this only when we are committing the whole index. Then theoretically the next operation after commit could start from a fully populated cache-tree in the index. When we are running a partial commit, the index file you are writing back is a temporary index only to build a tree object to record in the commit, which we already have done, and the temporary will be discarded. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html