On Tue, Feb 6, 2018 at 3:04 PM, Elijah Newren <newren@xxxxxxxxx> wrote: > > Does anyone have an idea what may have happened here or how to avoid it? According to Peff this got fixed https://public-inbox.org/git/20171020031630.44zvzh3d2vlhglv4@xxxxxxxxxxxxxxxxxxxxx/ and but you've had a corrupted repo from back when you were using an older version of Git. Did that repo exist before d0c39a49cc was rolled out? Then we can keep that hypothesis of "left-over corruption" as Peff put it.
