Re: [PATCH v2 2/2] do_compare_entry: use already-computed path

2016-01-05 Thread David Turner
On Mon, 2015-12-21 at 17:34 -0500, David Turner wrote: > In traverse_trees, we generate the complete traverse path for a Please replace with the attached version, which eliminates an unnecessary check.From 520cfbff15faa6de50d37b4a476b21dbe1598433 Mon Sep 17 00:00:00 2001 From: David Turner Date:

[PATCH v2 2/2] do_compare_entry: use already-computed path

2015-12-21 Thread David Turner
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. In