Jeff King <peff@xxxxxxxx> writes: > 2. It "lies" about the commit by setting the parsed flag, > even though we didn't load any useful data into the > struct. This shouldn't matter for the UNINTERESTING > case, but we may later clear our flags and do another > traversal in the same process. While pretty unlikely, > it's possible that we could then look at the same > commit without the UNINTERESTING flag,... Yeah, if two ranges given to tbdiff to be compared are computed in-core, uninteresting boundary of one range is likely to be interesting on the other range.