Hi, Alexander Mills wrote:
> Yeah as long as git shouldnt fumble wrt concurrent access across repos, it > was most likely the same repo being accessed concurrently and that's what > was causing the issue. > > that being said, it would be really nice if git itself could handle > concurrent requests to the same repo, that definitely seems to be a > limitation. Instead of all these guesses, I'd prefer if you describe the actual symptoms. Git is meant to support concurrent accesses of the same repo as well, and I haven't heard of any rumors of that being broken, either. Sincerely, Jonathan
