From: Jeff King <peff@peff.net>
To: Aleksey Midenkov <midenok@gmail.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Bug: fatal: Unable to create '.../.git/index.lock': File exists.
Date: Thu, 2 May 2019 11:07:01 -0400 [thread overview]
Message-ID: <20190502150701.GA14906@sigill.intra.peff.net> (raw)
In-Reply-To: <CAF8BazAK_s89XY8-AAsSSbgOFgP03CLRZ50bLGPsc89bfnN7kQ@mail.gmail.com>
On Thu, May 02, 2019 at 04:45:36PM +0300, Aleksey Midenkov wrote:
> > Assuming that kdevelop is just running "git status" in the background,
> > though, there's an easier solution. If it uses "git --no-optional-locks
> > status" instead, that will instruct it not to take the index lock at
> > all.
>
> And can we disable optional locks at git configuration level? Because
> changing source code of each application that is not aware of this
> option is not an easier solution.
Since the decision of whether to use the locks is dependent on the
operation being performed, it's an environment variable and not a config
option. You should be able to do:
GIT_OPTIONAL_LOCKS=0 kdevelop
and any commands run by kdevelop will avoid taking locks when they can
(but for now, the only command which does this is git-status anyway).
-Peff
next prev parent reply other threads:[~2019-05-02 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF8BazDu_GqoCPBQ-gEJ+q8n1aWSjf_TOV7bDE5VCQkDgBjyfQ@mail.gmail.com>
2019-04-29 11:02 ` Bug: fatal: Unable to create '.../.git/index.lock': File exists Aleksey Midenkov
2019-04-29 11:34 ` Duy Nguyen
2019-04-30 11:19 ` Aleksey Midenkov
2019-04-30 17:41 ` Jeff King
2019-05-01 7:15 ` Aleksey Midenkov
2019-05-01 18:36 ` Jeff King
2019-05-02 13:45 ` Aleksey Midenkov
2019-05-02 15:07 ` Jeff King [this message]
2019-05-02 16:38 ` Duy Nguyen
2019-05-02 16:58 ` Jeff King
2019-05-02 17:24 ` Duy Nguyen
2019-05-03 9:47 ` Johannes Schindelin
2019-05-03 10:22 ` Duy Nguyen
2019-05-03 5:42 ` Duy Nguyen
2019-04-29 21:10 ` Johannes Schindelin
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=20190502150701.GA14906@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=midenok@gmail.com \
--cc=pclouds@gmail.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.
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 NNTP newsgroup(s).