On Tue, Aug 08, 2017 at 06:25:24PM +0100, Adam Dinwoodie wrote: > I'm running a bisect overnight to try to isolate the commit on the left > merge parent that seems to be interacting badly with the commit on the > right, and will send in the results from that when I have them.
For the sake of interest, I've tracked down the problem to commit v2.9.0-3-g9e4e8a64c. That changed t3700 so it would no longer add all extant paths to the index, meaning a later `git reset --hard` wouldn't remove them.
