Re: [PATCH] perf: work around the tested repo having an index.lock
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 5, 2017, 02:04 UTC
- Message-ID
- <xmqq60gbur4i.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <20170604082919.y5g34udvyjfaqtve@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> I don't really mind addressing this one case that much. I'm not sure > that we want to accrue a pile of band-aids here that causes a > maintenance burden and doesn't really solve the problem completely. One > way to do that is to say no to the first band-aid.
Yup, that was where my objection came from.
> But we could also > apply it and see what happens. At the very worst it's a few extra lines > of code, and we can start to get worried on the second or third > band-aid.
That's OK as well. But we should resolve now that we will rip all of them out once we start seeing the second or third band-aid. I really do not want to see the "accring a pile of band aids" in our future.