Jeff King <peff@xxxxxxxx> writes: > On Tue, Jul 31, 2018 at 01:23:04PM -0400, Jeff King wrote: > ... > So here it is fixed, and with a commit message. I'm not happy to omit a > regression test, but I actually couldn't come up with a minimal one that > tickled the problem, because we're playing around with heuristics. So I > compensated by probably over-explaining in the commit message. But Have you tried to apply the message yourself? I'll fix it up but the hint to answer that question is in two extra pair of scissors. > clearly this is not a well-tested code path given the length of time > between introducing and detecting the bug. Thanks for writing it up. The patch itself still looks correct, too.
