Michael Haggerty <mhagger@xxxxxxxxxxxx> writes: > At GitHub we were seeing occasional lock contention over packed-refs. > It wasn't very common, but when you have as much git traffic as we > have, anything that *can* happen *will* happen. > > The problem is that Git only tries to acquire locks a single time. If > that attempt fails, the whole process fails. So, for example, if two > processes are trying to delete two different references, one of them > can fail due to inability to acquire the packed-refs lock, even though > it could have succeeded if it had just waited a moment. Yeah, try and abort may be perfectly fine for Git used interactively by humans, but is totally unsuitable for the server side. Thanks for looking into this. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html