From: Duy Nguyen <pclouds@gmail.com>
To: Ian Norton <inorton@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Stefan Beller <sbeller@google.com>
Subject: Re: Are concurrent git operations on the same repo safe?
Date: Tue, 6 Feb 2018 17:16:56 +0700 [thread overview]
Message-ID: <CACsJy8Bhu6RvedKgOx8uExrJuo0-b66JvnZA9d9v4Uk6mSwPQQ@mail.gmail.com> (raw)
In-Reply-To: <CAGUnuBHY9nQvGiROm4S_JvBWMrzieHC1FE50fJqxaauzZhH7xw@mail.gmail.com>
On Tue, Feb 6, 2018 at 3:16 AM, Ian Norton <inorton@gmail.com> wrote:
> Hi all,
>
> I'm generally used to the idea that if a thing is not marked as
> "thread-safe" then it isn't thread safe, but I thought I'd ask anyway
> to be sure.
>
> Is it safe for me to do several operations with git concurrently on
> the same local repo?
Off the top of my head, object database access (e.g. things in
.git/objects), refs updates (.git/refs) and .git/index should handle
concurrent operations fine (or in the worst case you get "some
operation is ongoing, aborted" and you need to try again but not
corruption or anything else). I think we generally try to make it safe
concurrently.
> Specifically I'm trying to speed up "git
> submodule update" by doing several at the same time. I've noticed
> some odd side effects afterwards though when trying to commit changes
> to my super project.
submodule is a hot area with lots of development lately I think,
perhaps you're seeing some bugs... CCing at least one submodule
person...
> Apologies if this is answered elsewhere, my google-foo is weak today.
>
> Many thanks
>
> Ian
--
Duy
next prev parent reply other threads:[~2018-02-06 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 20:16 Are concurrent git operations on the same repo safe? Ian Norton
2018-02-06 10:16 ` Duy Nguyen [this message]
2018-02-06 17:30 ` Stefan Beller
2018-02-06 20:10 ` Jonathan Nieder
2018-02-06 20:26 ` Ian Norton
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACsJy8Bhu6RvedKgOx8uExrJuo0-b66JvnZA9d9v4Uk6mSwPQQ@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=inorton@gmail.com \
--cc=sbeller@google.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).