Re: [PATCH] do_compare_entry: use already-computed path

David Turner writes: > In traverse_trees, we generate the complete traverse path for a > traverse_info. Later, in do_compare_entry, we used to go do a bunch > of work to compare the traverse_info to a cache_entry's name without > computing that path. But since we

[PATCH] do_compare_entry: use already-computed path

In traverse_trees, we generate the complete traverse path for a traverse_info. Later, in do_compare_entry, we used to go do a bunch of work to compare the traverse_info to a cache_entry's name without computing that path. But since we already have that path, we don't need to do all that work.