git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: concurrent access to multiple local git repos is error prone

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 5, 2018, 06:13 UTC
Message-ID
<20180805061312.GA44140@aiede.svl.corp.google.com>
In-Reply-To
<CA+KyZp5i0EXPJ10v+SXmHWCYvZ7=XT8K8gcka0qxCBYXq=OevA@mail.gmail.com>
Hi,
Alexander Mills wrote:
Show 7 quoted lines
> 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

Previous: Jonathan NiederNext: Jonathan Nieder
Message 4 of 11 in “concurrent access to multiple local git repos is error prone”
  1. Alexander MillsAug 4, 2018
  2. Alexander MillsAug 4, 2018
  3. Jonathan NiederAug 5, 2018
  4. Jonathan NiederAug 5, 2018
  5. Jonathan NiederAug 5, 2018
  6. Alexander MillsAug 5, 2018
  7. exit code in git diff-index [was: Re: concurrent access to multiple local git repos is error prone]Thomas Gummerer, Aug 5, 2018
  8. Alexander MillsAug 6, 2018
  9. Alexander MillsAug 6, 2018
  10. Jonathan NiederAug 6, 2018
  11. Duy NguyenAug 6, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.