From: Jonathan Nieder <jrnieder@gmail.com>
To: Alexander Mills <alexander.d.mills@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: concurrent access to multiple local git repos is error prone
Date: Sat, 4 Aug 2018 23:13:12 -0700 [thread overview]
Message-ID: <20180805061312.GA44140@aiede.svl.corp.google.com> (raw)
In-Reply-To: <CA+KyZp5i0EXPJ10v+SXmHWCYvZ7=XT8K8gcka0qxCBYXq=OevA@mail.gmail.com>
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
next prev parent reply other threads:[~2018-08-05 6:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 21:47 concurrent access to multiple local git repos is error prone Alexander Mills
2018-08-04 21:48 ` Alexander Mills
2018-08-05 1:46 ` Jonathan Nieder
[not found] ` <CA+KyZp5i0EXPJ10v+SXmHWCYvZ7=XT8K8gcka0qxCBYXq=OevA@mail.gmail.com>
2018-08-05 6:13 ` Jonathan Nieder [this message]
[not found] ` <CA+KyZp4Yc4_Xaw3v+BPwxi_PW75=GXmj=Re7EpsurXi2_hMc9w@mail.gmail.com>
2018-08-05 8:11 ` Jonathan Nieder
2018-08-05 19:17 ` Alexander Mills
2018-08-05 19:34 ` exit code in git diff-index [was: Re: concurrent access to multiple local git repos is error prone] Thomas Gummerer
2018-08-06 7:36 ` concurrent access to multiple local git repos is error prone Alexander Mills
2018-08-06 7:38 ` Alexander Mills
2018-08-06 14:32 ` Jonathan Nieder
2018-08-06 15:22 ` Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180805061312.GA44140@aiede.svl.corp.google.com \
--to=jrnieder@gmail.com \
--cc=alexander.d.mills@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox