On Tue, Jan 12, 2016 at 05:09:07AM +0100, Michael Haggerty wrote:
quoted
This patch could go to maint. I don't know if it's worth the trouble. I
was unable to figure out a way to trigger this reliably (hence no
tests). The two ways I considered were:
- "chmod -w .git", but it results in a die() already
- the bug I'm fixing in 2/2; but we don't want to rely on that in our
test suite, since I'm about to fix it. :-/
A locking conflict is an easy way to trigger this error:
[...]
Thanks, that's a good suggestion; I'll add a test in the re-roll.
-Peff