On 1/4/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote:
> Johannes, I remember suggesting to do index flush for all > entries instead for every entry. It is already quite time ago, > but ... was there any reasons for not doing this? I wanted to be on the safe side, and eventually look through the code again for possible problems. I think what you did is safe, since you moved the call from process_entry() to its sole caller, merge_trees().
Me too, just wondered why didn't we do this back then. Anyway, my "monster-merge" and the builtin tests pass with no visible problems.
However, I was wondering if the index has to be written at all. I expect the written index (except the last one, of course) to have no user...
Good question... - 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